Systems and methods for providing hotspot connectivity to a vehicle communication network access point in a network of moving things, for example including autonomous vehicles

ABSTRACT

Systems and methods for managing connectivity in a network of moving things. As non-limiting examples, various aspects of this disclosure provide systems and methods for managing connectivity in a network in which at least a portion of the network access points are moving.

CROSS-REFERENCE TO RELATED APPLICATIONS/INCORPORATION BY REFERENCE

This patent application makes reference to, claims priority to, andclaims benefit from U.S. Provisional Application Ser. No. 62/222,121,titled “Systems and Methods for Managing Connectivity in a Network ofMoving Things,” filed on Sep. 22, 2015, which is hereby incorporatedherein by reference in its entirety. The present application is alsorelated to U.S. Provisional Patent Application Ser. No. 62/222,192,titled “Communication Network of Moving Things,” filed on Sep. 22, 2015;U.S. Provisional Application Ser. No. 62/221,997, titled “IntegratedCommunication Network for a Network of Moving Things,” filed on Sep. 22,2015; U.S. Provisional Application Ser. No. 62/222,016, titled “Systemsand Methods for Synchronizing a Network of Moving Things,” filed on Sep.22, 2015; U.S. Provisional Application Ser. No. 62/222,042, titled“Systems and Methods for Managing a Network of Moving Things,” filed onSep. 22, 2015; U.S. Provisional Application Ser. No. 62/222,066, titled“Systems and Methods for Monitoring a Network of Moving Things,” filedon Sep. 22, 2015; U.S. Provisional Application Ser. No. 62/222,077,titled “Systems and Methods for Detecting and Classifying Anomalies in aNetwork of Moving Things,” filed on Sep. 22, 2015; U.S. ProvisionalApplication Ser. No. 62/222,098, titled “Systems and Methods forManaging Mobility in a Network of Moving Things,” filed on Sep. 22,2015; U.S. Provisional Application Ser. No. 62/222,121, titled “Systemsand Methods for Managing Connectivity a Network of Moving Things,” filedon Sep. 22, 2015; U.S. Provisional Application Ser. No. 62/222,135,titled “Systems and Methods for Collecting Sensor Data in a Network ofMoving Things,” filed on Sep. 22, 2015; U.S. Provisional ApplicationSer. No. 62/222,145, titled “Systems and Methods for Interfacing with aNetwork of Moving Things,” filed on Sep. 22, 2015; U.S. ProvisionalApplication Ser. No. 62/222,150, titled “Systems and Methods forInterfacing with a User of a Network of Moving Things,” filed on Sep.22, 2015; U.S. Provisional Application Ser. No. 62/222,168, titled“Systems and Methods for Data Storage and Processing for a Network ofMoving Things,” filed on Sep. 22, 2015; U.S. Provisional ApplicationSer. No. 62/222,183, titled “Systems and Methods for Vehicle TrafficManagement in a Network of Moving Things,” filed on Sep. 22, 2015; U.S.Provisional Application Ser. No. 62/222,186, titled “Systems and Methodsfor Environmental Management in a Network of Moving Things,” filed onSep. 22, 2015; U.S. Provisional Application Ser. No. 62/222,190, titled“Systems and Methods for Port Management in a Network of Moving Things,”filed on Sep. 22, 2015; U.S. Provisional Application Ser. No.62/244,828, titled “Utilizing Historical Data to Correct GPS Data in aNetwork of Moving Things,” filed on Oct. 22, 2015; U.S. ProvisionalApplication Ser. No. 62/244,930, titled “Using Anchors to Correct GPSData in a Network of Moving Things,” filed on Oct. 22, 2015; U.S.Provisional Application Ser. No. 62/246,368, titled “Systems and Methodsfor Inter-Application Communication in a Network of Moving Things,”filed on Oct. 26, 2015; U.S. Provisional Application Ser. No.62/246,372, titled “Systems and Methods for Probing and ValidatingCommunication in a Network of Moving Things,” filed on Oct. 26, 2015;U.S. Provisional Application Ser. No. 62/250,544, titled “Adaptive RateControl for Vehicular Networks,” filed on Nov. 4, 2015; U.S. ProvisionalApplication Ser. No. 62/273,878, titled “Systems and Methods forReconfiguring and Adapting Hardware in a Network of Moving Things,”filed on Dec. 31, 2015; U.S. Provisional Application Ser. No.62/253,249, titled “Systems and Methods for Optimizing Data Gathering ina Network of Moving Things,” filed on Nov. 10, 2015; U.S. ProvisionalApplication Ser. No. 62/257,421, titled “Systems and Methods for DelayTolerant Networking in a Network of Moving Things,” filed on Nov. 19,2015; U.S. Provisional Application Ser. No. 62/265,267, titled “Systemsand Methods for Improving Coverage and Throughput of Mobile AccessPoints in a Network of Moving Things,” filed on Dec. 9, 2015; U.S.Provisional Application Ser. No. 62/270,858, titled “ChannelCoordination in a Network of Moving Things,” filed on Dec. 22, 2015;U.S. Provisional Application Ser. No. 62/257,854, titled “Systems andMethods for Network Coded Mesh Networking in a Network of MovingThings,” filed on Nov. 20, 2015; U.S. Provisional Application Ser. No.62/260,749, titled “Systems and Methods for Improving Fixed Access PointCoverage in a Network of Moving Things,” filed on Nov. 30, 2015; U.S.Provisional Application Ser. No. 62/273,715, titled “Systems and Methodsfor Managing Mobility Controllers and Their Network Interactions in aNetwork of Moving Things,” filed on Dec. 31, 2015; U.S. ProvisionalApplication Ser. No. 62/281,432, titled “Systems and Methods forManaging and Triggering Handovers of Mobile Access Points in a Networkof Moving Things,” filed on Jan. 21, 2016; U.S. Provisional ApplicationSer. No. 62/268,188, titled “Captive Portal-related Control andManagement in a Network of Moving Things,” filed on Dec. 16, 2015; U.S.Provisional Application Ser. No. 62/270,678, titled “Systems and Methodsto Extrapolate High-Value Data from a Network of Moving Things,” filedon Dec. 22, 2015; U.S. Provisional Application Ser. No. 62/272,750,titled “Systems and Methods for Remote Software Update and Distributionin a Network of Moving Things,” filed on Dec. 30, 2015; U.S. ProvisionalApplication Ser. No. 62/278,662, titled “Systems and Methods for RemoteConfiguration Update and Distribution in a Network of Moving Things,”filed on Jan. 14, 2016; U.S. Provisional Application Ser. No.62/286,243, titled “Systems and Methods for Adapting a Network of MovingThings Based on User Feedback,” filed on Jan. 22, 2016; U.S. ProvisionalApplication Ser. No. 62/278,764, titled “Systems and Methods toGuarantee Data Integrity When Building Data Analytics in a Network ofMoving Things,” Jan. 14, 2016; U.S. Provisional Application Ser. No.62/286,515, titled “Systems and Methods for Self-Initialization andAutomated Bootstrapping of Mobile Access Points in a Network of MovingThings,” filed on Jan. 25, 2016; U.S. Provisional Application Ser. No.62/295,602, titled “Systems and Methods for Power Management in aNetwork of Moving Things,” filed on Feb. 16, 2016; and U.S. ProvisionalApplication Ser. No. 62/299,269, titled “Systems and Methods forAutomating and Easing the Installation and Setup of the InfrastructureSupporting a Network of Moving Things,” filed on Feb. 24, 2016; each ofwhich is hereby incorporated herein by reference in its entirety for allpurposes.

BACKGROUND

Current communication networks are unable to adequately supportcommunication environments involving moving networks. As a non-limitingexample, current communication networks are unable to adequately manageconnectivity in a network comprising a complex array of both moving andstatic nodes (e.g., the Internet of moving things). Limitations anddisadvantages of conventional methods and systems will become apparentto one of skill in the art, through comparison of such approaches withsome aspects of the present methods and systems set forth in theremainder of this disclosure with reference to the drawings.

BRIEF DESCRIPTION OF SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 shows a block diagram of a communication network, in accordancewith various aspects of this disclosure.

FIG. 2 shows a block diagram of a communication network, in accordancewith various aspects of this disclosure.

FIG. 3 shows a diagram of a metropolitan area network, in accordancewith various aspects of this disclosure.

FIG. 4 shows a block diagram of a communication network, in accordancewith various aspects of this disclosure.

FIGS. 5A-5C show a plurality of network configurations illustrating theflexibility and/or and resiliency of a communication network, inaccordance with various aspects of this disclosure.

FIG. 6 shows a block diagram of an example communication network, inaccordance with various aspects of the present disclosure.

FIG. 7 shows a block diagram of an example communication network, inaccordance with various aspects of the present disclosure.

FIG. 8 shows a block diagram of an example communication network, inaccordance with various aspects of the present disclosure.

FIG. 9 shows a flow diagram of an example method for managingconnectivity, in accordance with various aspects of the presentdisclosure.

FIG. 10 shows a block diagram of an example network node, in accordancewith various aspects of the present disclosure.

SUMMARY

Various aspects of this disclosure provide systems and methods formanaging connectivity in a network of moving things. As non-limitingexamples, various aspects of this disclosure provide systems and methodsfor managing connectivity in a network in which at least a portion ofthe network access points are moving.

DETAILED DESCRIPTION OF VARIOUS ASPECTS OF THE DISCLOSURE

As utilized herein the terms “circuits” and “circuitry” refer tophysical electronic components (i.e., hardware) and any software and/orfirmware (“code”) that may configure the hardware, be executed by thehardware, and or otherwise be associated with the hardware. As usedherein, for example, a particular processor and memory (e.g., a volatileor non-volatile memory device, a general computer-readable medium, etc.)may comprise a first “circuit” when executing a first one or more linesof code and may comprise a second “circuit” when executing a second oneor more lines of code. Additionally, a circuit may comprise analogand/or digital circuitry. Such circuitry may, for example, operate onanalog and/or digital signals. It should be understood that a circuitmay be in a single device or chip, on a single motherboard, in a singlechassis, in a plurality of enclosures at a single geographical location,in a plurality of enclosures distributed over a plurality ofgeographical locations, etc.

As utilized herein, circuitry is “operable” to perform a functionwhenever the circuitry comprises the necessary hardware and code (if anyis necessary) to perform the function, regardless of whether performanceof the function is disabled, or not enabled (e.g., by auser-configurable setting, factory setting or trim, etc.).

As utilized herein, “and/or” means any one or more of the items in thelist joined by “and/or”. As an example, “x and/or y” means any elementof the three-element set {(x), (y), (x, y)}. That is, “x and/or y” means“one or both of x and y.” As another example, “x, y, and/or z” means anyelement of the seven-element set {(x), (y), (z), (x, y), (x, z), (y, z),(x, y, z)}. That is, “x, y, and/or x” means “one or more of x, y, andz.” As utilized herein, the terms “e.g.,” and “for example” set offlists of one or more non-limiting examples, instances, or illustrations.

The terminology used herein is for the purpose of describing particularexamples only and is not intended to be limiting of the disclosure. Asused herein, the singular forms are intended to include the plural formsas well, unless the context clearly indicates otherwise. It will befurther understood that the terms “comprises,” “includes,” “comprising,”“including,” “has,” “have,” “having,” and the like when used in thisspecification, specify the presence of stated features, integers, steps,operations, elements, and/or components, but do not preclude thepresence or addition of one or more other features, integers, steps,operations, elements, components, and/or groups thereof.

It will be understood that, although the terms first, second, etc. maybe used herein to describe various elements, these elements should notbe limited by these terms. These terms are only used to distinguish oneelement from another element. Thus, for example, a first element, afirst component or a first section discussed below could be termed asecond element, a second component or a second section without departingfrom the teachings of the present disclosure. Similarly, various spatialterms, such as “upper,” “lower,” “side,” and the like, may be used indistinguishing one element from another element in a relative manner. Itshould be understood, however, that components may be oriented indifferent manners, for example an electronic device may be turnedsideways so that its “top” surface is facing horizontally and its “side”surface is facing vertically, without departing from the teachings ofthe present disclosure.

With the proliferation of the mobile and/or static things (e.g.,devices, machines, people, etc.) and logistics for such things to becomeconnected to each other (e.g., in the contexts of smart logistics,transportation, environmental sensing, etc.), a platform that is forexample always-on, robust, scalable and secure that is capable ofproviding connectivity, services and Internet access to such things (orobjects), anywhere and anytime is desirable. Efficient power utilizationwithin the various components of such system is also desirable.

Accordingly, various aspects of the present disclosure provide afully-operable, always-on, responsive, robust, scalable, secureplatform/system/architecture to provide connectivity, services andInternet access to all mobile things and/or static things (e.g.,devices, machines, people, access points, end user devices, sensors,etc.) anywhere and anytime, while operating in an energy-efficientmanner.

Various aspects of the present disclosure provide a platform that isflexibly configurable and adaptable to the various requirements,features, and needs of different environments, where each environmentmay be characterized by a respective level of mobility and density ofmobile and/or static things, and the number and/or types of access tothose things. Characteristics of various environments may, for example,include high mobility of nodes (e.g., causing contacts or connections tobe volatile), high number of neighbors, high number of connected mobileusers, mobile access points, availability of multiple networks andtechnologies (e.g., sometimes within a same area), etc. For example, themode of operation of the platform may be flexibly adapted fromenvironment to environment, based on each environment's respectiverequirements and needs, which may be different from other environments.Additionally for example, the platform may be flexibly optimized (e.g.,at design/installation time and/or in real-time) for different purposes(e.g., to reduce the latency, increase throughput, reduce powerconsumption, load balance, increase reliability, make more robust withregard to failures or other disturbances, etc.), for example based onthe content, service or data that the platform provides or handleswithin a particular environment.

In accordance with various aspects of the present disclosure, manycontrol and management services (e.g., mobility, security, routing,etc.) are provided on top of the platform (e.g., directly, using controloverlays, using containers, etc.), such services being compatible withthe services currently deployed on top of the Internet or othercommunication network(s).

The communication network (or platform), in whole or in part, may forexample be operated in public and/or private modes of operation, forexample depending on the use case. The platform may, for example,operate in a public or private mode of operation, depending on theuse-case (e.g., public Internet access, municipal environment sensing,fleet operation, etc.).

Additionally for example, in an implementation in which various networkcomponents are mobile, the transportation and/or signal controlmechanisms may be adapted to serve the needs of the particularimplementation. Also for example, wireless transmission power and/orrate may be adapted (e.g., to mitigate interference, to reduce powerconsumption, to extend the life of network components, etc.

Various example implementations of a platform, in accordance withvarious aspects of the present disclosure, are capable of connectingdifferent subsystems, even when various other subsystems that maynormally be utilized are unavailable. For example, the platform maycomprise various built-in redundancies and fail-recovery mechanisms. Forexample, the platform may comprise a self-healing capability,self-configuration capability, self-adaptation capability, etc. Theprotocols and functions of the platform may, for example, be prepared tobe autonomously and smoothly configured and adapted to the requirementsand features of different environments characterized by different levelsof mobility and density of things (or objects), the number/types ofaccess to those things. For example, various aspects of the platform maygather context parameters that can influence any or all decisions. Suchparameters may, for example, be derived locally, gathered from aneighborhood, Fixed APs, the Cloud, etc. Various aspects of the platformmay also, for example, ask for historical information to feed any of thedecisions, where such information can be derived from historical data,from surveys, from simulators, etc. Various aspects of the platform mayadditionally, for example, probe or monitor decisions made throughoutthe network, for example to evaluate the network and/or the decisionsthemselves in real-time. Various aspects of the platform may further,for example, enforce the decisions in the network (e.g., afterevaluating the probing results). Various aspects of the platform may,for example, establish thresholds to avoid any decision that is to beconstantly or repeatedly performed without any significant advantage(e.g., technology change, certificate change, IP change, etc.). Variousaspects of the platform may also, for example, learn locally (e.g., withthe decisions performed) and dynamically update the decisions.

In addition to (or instead of) failure robustness, a platform mayutilize multiple connections (or pathways) that exist between distinctsub-systems or elements within the same sub-system, to increase therobustness and/or load-balancing of the system.

The following discussion will present examples of the functionalityperformed by various example subsystems of the communication network. Itshould be understood that the example functionality discussed hereinneed not be performed by the particular example subsystem or by a singlesubsystem. For example, the subsystems present herein may interact witheach other, and data or control services may be deployed either in acentralized way, or having their functionalities distributed among thedifferent subsystems, for example leveraging the cooperation between theelements of each subsystem.

Various aspects of the present disclosure provide a communicationnetwork (e.g., a city-wide vehicular network, a shipping port-sizedvehicular network, a campus-wide vehicular network, etc.) that utilizesvehicles (e.g., automobiles, buses, trucks, boats, forklifts, etc.) asWi-Fi hotspots. Note that Wi-Fi is generally used throughout thisdiscussion as an example, but the scope of various aspects of thisdisclosure is not limited thereto. For example, other wireless LANtechnologies, PAN technologies, MAN technologies, etc., may be utilized.Such utilization may, for example, provide cost-effective ways to gathersubstantial amounts of urban data, and provide for the efficientoffloading of traffic from congested cellular networks (or othernetworks). In controlled areas (e.g., ports, harbors, etc.) with manyvehicles, a communication network in accordance with various aspects ofthis disclosure may expand the wireless coverage of existing enterpriseWi-Fi networks, for example providing for real-time communication withvehicle drivers (e.g., human, computer-controlled, etc.) and othermobile employees without the need for SIM cards or cellular (or othernetwork) data plans.

Vehicles may have many advantageous characteristics that make themuseful as Wi-Fi (or general wireless) hotspots. For example, vehiclesgenerally have at least one battery, vehicles are generally denselyspread over the city at street level and/or they are able to establishmany contacts with each other in a controlled space, and vehicles cancommunicate with 10× the range of normal Wi-Fi in the 5.9 GHz frequencyband, reserved for intelligent transportation systems in the EU, theU.S., and elsewhere. Note that the scope of this disclosure is notlimited to such 5.9 GHz wireless communication. Further, vehicles areable to effectively expand their coverage area into a swath over aperiod of time, enabling a single vehicle access point to interact withsubstantially more data sources over the period of time.

In accordance with various aspects of the present disclosure, anaffordable multi-network on-board unit (OBU) is presented. Note that theOBU may also be referred to herein as a mobile access point, Mobile AP,MAP, etc. The OBU may, for example, comprise a plurality of networkinginterfaces (e.g., Wi-Fi, 802.11p, 4G, Bluetooth, UWB, etc.). The OBUmay, for example, be readily installed in or on private and/or publicvehicles (e.g., individual user vehicles, vehicles of private fleets,vehicles of public fleets, etc.). The OBU may, for example, be installedin transportation fleets, waste management fleets, law enforcementfleets, emergency services, road maintenance fleets, taxi fleets,aircraft fleets, etc. The OBU may, for example, be installed in or on avehicle or other structure with free mobility or relatively limitedmobility. The OBU may also, for example, be carried by a person orservice animal, mounted to a bicycle, mounted to a moving machine ingeneral, mounted to a container, etc.

The OBUs may, for example, operate to connect passing vehicles to thewired infrastructure of one or more network providers, telecomoperators, etc. In accordance with the architecture, hardware, andsoftware functionality discussed herein, vehicles and fleets can beconnected not just to the cellular networks (or other wide area ormetropolitan area networks, etc.) and existing Wi-Fi hotspots spreadover a city or a controlled space, but also to other vehicles (e.g.,utilizing multi-hop communications to a wired infrastructure, single ormulti-hop peer-to-peer vehicle communication, etc.). The vehicles and/orfleets may, for example, form an overall mesh of communication links,for example including the OBUs and also fixed Access Points (APs)connected to the wired infrastructure (e.g., a local infrastructure,etc.). Note that OBUs herein may also be referred to as “Mobile APs,”“mobile hotspots,” “MAPs,” etc. Also note that fixed access points mayalso be referred to herein as Road Side Units (RSUs), Fixed APs, FAPs,etc.

In an example implementation, the OBUs may communicate with the FixedAPs utilizing a relatively long-range protocol (e.g., 802.11p, etc.),and the Fixed APs may, in turn, be hard wired to the wiredinfrastructure (e.g., via cable, tethered optical link, etc.). Note thatFixed APs may also, or alternatively, be coupled to the infrastructurevia wireless link (e.g., 802.11p, etc.). Additionally, clients or userdevices may communicate with the OBUs using one or more relativelyshort-range protocols (e.g., Wi-Fi, Bluetooth, UWB, etc.). The OBUs, forexample having a longer effective wireless communication range thantypical Wi-Fi access points or other wireless LAN/PAN access points(e.g., at least for links such as those based on 802.11p, etc.), arecapable of substantially greater coverage areas than typical Wi-Fi orother wireless LAN/PAN access points, and thus fewer OBUs are necessaryto provide blanket coverage over a geographical area.

The OBU may, for example, comprise a robust vehicular networking module(e.g., a connection manager) which builds on long-range communicationprotocol capability (e.g., 802.11p, etc.). For example, in addition tocomprising 802.11p (or other long-range protocol) capability tocommunicate with Fixed APs, vehicles, and other nodes in the network,the OBU may comprise a network interface (e.g., 802.11a/b/g/n, 802.11ac,802.11af, any combination thereof, etc.) to provide wireless local areanetwork (WLAN) connectivity to end user devices, sensors, fixed Wi-Fiaccess points, etc. For example, the OBU may operate to providein-vehicle Wi-Fi Internet access to users in and/or around the vehicle(e.g., a bus, train car, taxi cab, public works vehicle, etc.). The OBUmay further comprise one or more wireless backbone communicationinterfaces (e.g., cellular network interfaces, etc.). Though in variousexample scenarios, a cellular network interface (or other wirelessbackbone communication interface) might not be the preferred interfacefor various reasons (e.g., cost, power, bandwidth, etc.), the cellularnetwork interface may be utilized to provide connectivity ingeographical areas that are not presently supported by a Fixed AP, maybe utilized to provide a fail-over communication link, may be utilizedfor emergency communications, may be utilized to subscribe to localinfrastructure access, etc. The cellular network interface may also, forexample, be utilized to allow the deployment of solutions that aredependent on the cellular network operators.

An OBU, in accordance with various aspects of the present disclosure,may for example comprise a smart connection manager that can select thebest available wireless link(s) (e.g., Wi-Fi, 802.11p, cellular, vehiclemesh, etc.) with which to access the Internet. The OBU may also, forexample, provide geo-location capabilities (e.g., GPS, etc.), motiondetection sensors to determine if the vehicle is in motion, and a powercontrol subsystem (e.g., to ensure that the OBU does not deplete thevehicle battery, etc.). The OBU may, for example, comprise any or all ofthe sensors (e.g., environmental sensors, etc.) discussed herein.

The OBU may also, for example, comprise a manager that managesmachine-to-machine data acquisition and transfer (e.g., in a real-timeor delay-tolerant fashion) to and from the Cloud. For example, the OBUmay log and/or communicate information of the vehicles.

The OBU may, for example, comprise a connection and/or routing managerthat operates to perform routing of communications in avehicle-to-vehicle/vehicle-to-infrastructure multi-hop communication. Amobility manager (or controller, MC) may, for example, ensure thatcommunication sessions persist over one or more handoff(s) (alsoreferred to herein as a “handover” or “handovers”) (e.g., betweendifferent Mobile APs, Fixed APs, base stations, hot spots, etc.), amongdifferent technologies (e.g., 802.11p, cellular, Wi-Fi, satellite,etc.), among different MCs (e.g., in a fail-over scenario, loadredistribution scenario, etc.), across different interfaces (or ports),etc. Note that the MC may also be referred to herein as a Local MobilityAnchor (LMA), a Network Controller (NC), etc. Note that the MC, or aplurality thereof, may for example be implemented as part of thebackbone, but may also, or alternatively, be implemented as part of anyof a variety of components or combinations thereof. For example, the MCmay be implemented in a Fixed AP (or distributed system thereof), aspart of an OBU (or a distributed system thereof), etc. Variousnon-limiting examples of system components and/or methods are providedin U.S. Provisional Application No. 62/222,098, filed Sep. 22, 2015, andtitled “Systems and Method for Managing Mobility in a Network of MovingThings,” the entire contents of which are hereby incorporated herein byreference. Note that in an example implementation including a pluralityof MCs, such MCs may be co-located and/or may be geographicallydistributed.

Various aspects of the present disclosure also provide a Cloud-basedservice-oriented architecture that handles the real-time management,monitoring and reporting of the network and clients, the functionalitiesrequired for data storage, processing and management, the Wi-Fi clientauthentication and Captive Portal display, etc.

A communication network (or component thereof) in accordance withvarious aspects of the present disclosure may, for example, support awide range of smart city applications (or controlled scenarios, orconnected scenarios, etc.) and/or use-cases, as described herein.

For example, an example implementation may operate to turn each vehicle(e.g., both public and private taxis, buses, trucks, etc.) into a MobileAP (e.g., a mobile Wi-Fi hotspot), offering Internet access toemployees, passengers and mobile users travelling in the city, waitingin bus stops, sitting in parks, etc. Moreover, through an examplevehicular mesh network formed between vehicles and/or fleets ofvehicles, an implementation may be operable to offload cellular trafficthrough the mobile Wi-Fi hotspots and/or Fixed APs (e.g., 802.11p-basedAPs) spread over the city and connected to the wired infrastructure ofpublic or private telecom operators in strategic places, while ensuringthe widest possible coverage at the lowest possible cost.

An example implementation (e.g., of a communication network and/orcomponents thereof) may, for example, be operable as a massive urbanscanner that gathers large amounts of data (e.g., continuously)on-the-move, actionable or not, generated by a myriad of sourcesspanning from the in-vehicle sensors or On Board Diagnostic System port(e.g., OBD2, etc.), external Wi-Fi/Bluetooth-enabled sensing unitsspread over the city, devices of vehicles' drivers and passengers (e.g.,information characterizing such devices and/or passengers, etc.),positioning system devices (e.g., position information, velocityinformation, trajectory information, travel history information, etc.),etc.

Depending on the use case, the OBU may for example process (or computer,transform, manipulate, aggregate, summarize, etc.) the data beforesending the data from the vehicle, for example providing the appropriategranularity (e.g., value resolution) and sampling rates (e.g., temporalresolution) for each individual application. For example, the OBU may,for example, process the data in any manner deemed advantageous by thesystem. The OBU may, for example, send the collected data (e.g., rawdata, preprocessed data, information of metrics calculated based on thecollected data, etc.) to the Cloud (e.g., to one or more networkedservers coupled to any portion of the network) in an efficient andreliable manner to improve the efficiency, environmental impact andsocial value of municipal city operations and transportation services.Various example use cases are described herein.

In an example scenario in which public buses are moving along cityroutes and/or taxis are performing their private transportationservices, the OBU is able to collect large quantities of real-time datafrom the positioning systems (e.g., GPS, etc.), from accelerometermodules, etc. The OBU may then, for example, communicate such data tothe Cloud, where the data may be processed, reported and viewed, forexample to support such public or private bus and/or taxi operations,for example supporting efficient remote monitoring and scheduling ofbuses and taxis, respectively.

In an example implementation, small cameras (or other sensors) may becoupled to small single-board computers (SBCs) that are placed above thedoors of public buses to allow capturing image sequences of peopleentering and leaving buses, and/or on stops along the bus routes inorder to estimate the number of people waiting for a bus. Such data maybe gathered by the OBU in order to be sent to the Cloud. With such data,public transportation systems may detect peaks; overcrowded buses,routes and stops; underutilized buses, routes and stops; etc., enablingaction to be taken in real-time (e.g., reducing bus periodicity todecrease fuel costs and CO₂ emissions where and when passenger flows aresmaller, etc.) as well as detecting systematic transportation problems.

An OBU may, for example, be operable to communicate with any of avariety of Wi-Fi-enabled sensor devices equipped with a heterogeneouscollection of environmental sensors. Such sensors may, for example,comprise noise sensors (microphones, etc.), gas sensors (e.g., sensingCO, NO₂, O₃, volatile organic compounds (or VOCs), CO₂, etc.), smokesensors, pollution sensors, meteorological sensors (e.g., sensingtemperature, humidity, luminosity, particles, solar radiation, windspeed (e.g., anemometer), wind direction, rain (e.g., a pluviometer),optical scanners, biometric scanners, cameras, microphones, etc.). Suchsensors may also comprise sensors associated with users (e.g., vehicleoperators or passengers, passersby, etc.) and/or their personal devices(e.g., smart phones or watches, biometrics sensors, wearable sensors,implanted sensors, etc.). Such sensors may, for example, comprisesensors and/or systems associated with on-board diagnostic (OBD) unitsfor vehicles. Such sensors may, for example, comprise positioningsensors (e.g., GPS sensors, Galileo sensors, GLONASS sensors, etc.).Such sensors may, for example, comprise container sensors (e.g., garbagecan sensors, shipping container sensors, container environmentalsensors, container tracking sensors, etc.).

Once a vehicle enters the vicinity of such a sensor device, a wirelesslink may be established, so that the vehicle (or OBU thereof) cancollect sensor data from the sensor device and upload the collected datato a database in the Cloud. The appropriate action can then be taken. Inan example waste management implementation, several waste management (orcollection) trucks may be equipped with OBUs that are able toperiodically communicate with sensors installed on containers in orderto gather information about waste level, time passed since lastcollection, etc. Such information may then sent to the Cloud (e.g., to awaste management application coupled to the Internet, etc.) through thevehicular mesh network, in order to improve the scheduling and/orrouting of waste management trucks. Note that various sensors may alwaysbe in range of the Mobile AP (e.g., vehicle-mounted sensors). Note thatthe sensor may also (or alternatively) be mobile (e.g., a sensor mountedto another vehicle passing by a Mobile AP or Fixed AP, a drone-mountedsensor, a pedestrian-mounted sensor, etc.).

In an example implementation, for example in a controlled space (e.g., aport, harbor, airport, factory, plantation, mine, etc.) with manyvehicles, machines and employees, a communication network in accordancewith various aspects of the present disclosure may expand the wirelesscoverage of enterprise and/or local Wi-Fi networks, for example withoutresorting to a Telco-dependent solution based on SIM cards or cellularfees. In such an example scenario, apart from avoiding expensivecellular data plans, limited data rate and poor cellular coverage insome places, a communication network in accordance with various aspectsof the present disclosure is also able to collect and/or communicatelarge amounts of data, in a reliable and real-time manner, where suchdata may be used to optimize harbor logistics, transportationoperations, etc.

For example in a port and/or harbor implementation, by gatheringreal-time information on the position, speed, fuel consumption and CO₂emissions of the vehicles, the communication network allows a portoperator to improve the coordination of the ship loading processes andincrease the throughput of the harbor. Also for example, thecommunication network enables remote monitoring of drivers' behaviors,trucks' positions and engines' status, and then be able to providereal-time notifications to drivers (e.g., to turn on/off the engine,follow the right route inside the harbor, take a break, etc.), thusreducing the number and duration of the harbor services and trips.Harbor authorities may, for example, quickly detect malfunctioningtrucks and abnormal trucks' circulation, thus avoiding accidents inorder to increase harbor efficiency, security, and safety. Additionally,the vehicles can also connect to Wi-Fi access points from harbor localoperators, and provide Wi-Fi Internet access to vehicles' occupants andsurrounding harbor employees, for example allowing pilots to save timeby filing reports via the Internet while still on the water.

FIG. 1 shows a block diagram of a communication network 100, inaccordance with various aspects of this disclosure. Any or all of thefunctionality discussed herein may be performed by any or all of theexample components of the example network 100. Also, the example network100 may, for example, share any or all characteristics with the otherexample networks and/or network components 200, 300, 400, 500-570, 600,700, 800, 900, and 1000 discussed herein.

The example network 100, for example, comprises a Cloud that may, forexample comprise any of a variety of network level components. The Cloudmay, for example, comprise any of a variety of server systems executingapplications that monitor and/or control components of the network 100.Such applications may also, for example, manage the collection ofinformation from any of a large array of networked information sources,many examples of which are discussed herein. The Cloud (or a portionthereof) may also be referred to, at times, as an API. For example,Cloud (or a portion thereof) may provide one or more applicationprogramming interfaces (APIs) which other devices may use forcommunicating/interacting with the Cloud.

An example component of the Cloud may, for example, manageinteroperability with various multi-Cloud systems and architectures.Another example component (e.g., a Cloud service component) may, forexample, provide various Cloud services (e.g., captive portal services,authentication, authorization, and accounting (AAA) services, APIGateway services, etc.). An additional example component (e.g., aDevCenter component) may, for example, provide network monitoring and/ormanagement functionality, manage the implementation of software updates,etc. A further example component of the Cloud may manage data storage,data analytics, data access, etc. A still further example component ofthe Cloud may include any of a variety of third-partly applications andservices.

The Cloud may, for example, be coupled to the Backbone/CoreInfrastructure of the example network 100 via the Internet (e.g.,utilizing one or more Internet Service Providers). Though the Internetis provided by example, it should be understood that scope of thepresent disclosure is not limited thereto.

The Backbone/Core may, for example, comprise any one or more differentcommunication infrastructure components. For example, one or moreproviders may provide backbone networks or various components thereof.As shown in the example network 100 illustrated in FIG. 1, a Backboneprovider may provide wireline access (e.g., PSTN, fiber, cable, etc.).Also for example, a Backbone provider may provide wireless access (e.g.,Microwave, LTE/Cellular, 5G/TV Spectrum, etc.).

The Backbone/Core may also, for example, comprise one or more LocalInfrastructure Providers. The Backbone/Core may also, for example,comprise a private infrastructure (e.g., run by the network 100implementer, owner, etc.). The Backbone/Core may, for example, provideany of a variety of Backbone Services (e.g., AAA, Mobility, Monitoring,Addressing, Routing, Content services, Gateway Control services, etc.).

The Backbone/Core Infrastructure may comprise any of a variety ofcharacteristics, non-limiting examples of which are provided herein. Forexample, the Backbone/Core may be compatible with different wireless orwired technologies for backbone access. The Backbone/Core may also beadaptable to handle public (e.g., municipal, city, campus, etc.) and/orprivate (e.g., ports, campus, etc.) network infrastructures owned bydifferent local providers, and/or owned by the network implementer orstakeholder. The Backbone/Core may, for example, comprise and/orinterface with different Authentication, Authorization, and Accounting(AAA) mechanisms.

The Backbone/Core Infrastructure may, for example, support differentmodes of operation (e.g., L2 in port implementations, L3 in on-landpublic transportation implementations, utilizing any one or more of aplurality of different layers of digital IP networking, any combinationsthereof, equivalents thereof, etc.) or addressing pools. TheBackbone/Core may also for example, be agnostic to the Cloud provider(s)and/or Internet Service Provider(s). Additionally for example, theBackbone/Core may be agnostic to requests coming from any or allsubsystems of the network 100 (e.g., Mobile APs or OBUs (On BoardUnits), Fixed APs or RSUs (Road Side Units), MCs (Mobility Controllers)or LMAs (Local Mobility Anchors) or Network Controllers, etc.) and/orthird-party systems.

The Backbone/Core Infrastructure may, for example, comprise the abilityto utilize and/or interface with different data storage/processingsystems (e.g., MongoDB, MySql, Redis, etc.). The Backbone/CoreInfrastructure may further, for example, provide different levels ofsimultaneous access to the infrastructure, services, data, etc.

The example network 100 may also, for example, comprise a Fixed HotspotAccess Network. Various example characteristics of such a Fixed HotspotAccess Network 200 are shown at FIG. 2. The example network 200 may, forexample, share any or all characteristics with the other examplenetworks and/or network components 100, 300, 400, 500-570, 600, 700,800, 900, and 1000, discussed herein.

In the example network 200, the Fixed APs (e.g., the proprietary APs,the public third party APs, the private third party APs, etc.) may bedirectly connected to the local infrastructure provider and/or to thewireline/wireless backbone. Also for example, the example network 200may comprise a mesh between the various APs via wireless technologies.Note, however, that various wired technologies may also be utilizeddepending on the implementation. As shown, different fixed hotspotaccess networks can be connected to a same backbone provider, but mayalso be connected to different respective backbone providers. In anexample implementation utilizing wireless technology for backboneaccess, such an implementation may be relatively fault tolerant. Forexample, a Fixed AP may utilize wireless communications to the backbonenetwork (e.g., cellular, 3G, LTE, other wide or metropolitan areanetworks, etc.) if the backhaul infrastructure is down. Also forexample, such an implementation may provide for relatively easyinstallation (e.g., a Fixed AP with no cable power source that can beplaced virtually anywhere).

In the example network 200, the same Fixed AP can simultaneously provideaccess to multiple Fixed APs, Mobile APs (e.g., vehicle OBUs, etc.),devices, user devices, sensors, things, etc. For example, a plurality ofmobile hotspot access networks (e.g., OBU-based networks, etc.) mayutilize the same Fixed AP. Also for example, the same Fixed AP canprovide a plurality of simultaneous accesses to another single unit(e.g., another Fixed AP, Mobile AP, device, etc.), for example utilizingdifferent channels, different radios, etc.).

Note that a plurality of Fixed APs may be utilized forfault-tolerance/fail-recovery purposes. In an example implementation, aFixed AP and its fail-over AP may both be normally operational (e.g., ina same switch). Also for example, one or more Fixed APs may be placed inthe network at various locations in an inactive or monitoring mode, andready to become operational when needed (e.g., in response to a fault,in response to an emergency services need, in response to a data surge,etc.).

Referring back to FIG. 1, the example Fixed Hotspot Access Network isshown with a wireless communication link to a backbone provider (e.g.,to one or more Backbone Providers and/or Local InfrastructureProviders), to a Mobile Hotspot Access Network, to one or more End UserDevices, and to the Environment. Also, the example Fixed Hotspot AccessNetwork is shown with a wired communication link to one or more BackboneProviders, to the Mobile Hotspot Access Network, to one or more End UserDevices, and to the Environment. The Environment may comprise any of avariety of devices (e.g., in-vehicle networks, devices, and sensors;autonomous vehicle networks, devices, and sensors; maritime (orwatercraft) and port networks, devices, and sensors; generalcontrolled-space networks, devices, and sensors; residential networks,devices, and sensors; disaster recovery & emergency networks, devices,and sensors; military and aircraft networks, devices, and sensors; smartcity networks, devices, and sensors; event (or venue) networks, devices,and sensors; underwater and underground networks, devices, and sensors;agricultural networks, devices, and sensors; tunnel (auto, subway,train, etc.) networks, devices, and sensors; parking networks, devices,and sensors; security and surveillance networks, devices, and sensors;shipping equipment and container networks, devices, and sensors;environmental control or monitoring networks, devices, and sensors;municipal networks, devices, and sensors; waste management networks,devices, and sensors, road maintenance networks, devices, and sensors,traffic management networks, devices, and sensors; advertising networks,devices and sensors; etc.).

The example network 100 of FIG. 1 also comprises a Mobile Hotspot AccessNetwork. Various example characteristics of such a Mobile Hotspot AccessNetwork 300 are shown at FIG. 3. Note that various fixed networkcomponents (e.g., Fixed APs) are also illustrated. The example network300 may, for example, share any or all characteristics with the otherexample networks and/or network components 100, 200, 400, 500-570, 600,700, 800, 900, and 1000, discussed herein.

The example network 300 comprises a wide variety of Mobile APs (orhotspots) that provide access to user devices, provide for sensor datacollection, provide multi-hop connectivity to other Mobile APs, etc. Forexample, the example network 300 comprises vehicles from differentfleets (e.g., aerial, terrestrial, underground, (under)water, etc.). Forexample, the example network 300 comprises one or more massdistribution/transportation fleets, one or more mass passengertransportation fleets, private/public shared-user fleets, privatevehicles, urban and municipal fleets, maintenance fleets, drones,watercraft (e.g., boats, ships, speedboats, tugboats, barges, etc.),emergency fleets (e.g., police, ambulance, firefighter, etc.), etc.

The example network 300, for example, shows vehicles from differentfleets directly connected and/or mesh connected, for example using sameor different communication technologies. The example network 300 alsoshows fleets simultaneously connected to different Fixed APs, which mayor may not belong to different respective local infrastructureproviders. As a fault-tolerance mechanism, the example network 300 mayfor example comprise the utilization of long-range wirelesscommunication network (e.g., cellular, 3G, 4G, LTE, etc.) in vehicles ifthe local network infrastructure is down or otherwise unavailable. Asame vehicle (e.g., Mobile AP or OBU) can simultaneously provide accessto multiple vehicles, devices, things, etc., for example using a samecommunication technology (e.g., shared channels and/or differentrespective channels thereof) and/or using a different respectivecommunication technology for each. Also for example, a same vehicle canprovide multiple accesses to another vehicle, device, thing, etc., forexample using a same communication technology (e.g., shared channelsand/or different respective channels thereof, and/or using a differentcommunication technology).

Additionally, multiple network elements may be connected together toprovide for fault-tolerance or fail recovery, increased throughput, orto achieve any or a variety of a client's networking needs, many ofexamples of which are provided herein. For example, two Mobile APs (orOBUs) may be installed in a same vehicle, etc.

Referring back to FIG. 1, the example Mobile Hotspot Access Network isshown with a wireless communication link to a backbone provider (e.g.,to one or more Backbone Providers and/or Local InfrastructureProviders), to a Fixed Hotspot Access Network, to one or more End UserDevice, and to the Environment (e.g., to any one of more of the sensorsor systems discussed herein, any other device or machine, etc.). Thoughthe Mobile Hotspot Access Network is not shown having a wired link tothe various other components, there may (at least at times) be such awired link, at least temporarily.

The example network 100 of FIG. 1 also comprises a set of End-UserDevices. Various example end user devices are shown at FIG. 4. Note thatvarious other network components (e.g., Fixed Hotspot Access Networks,Mobile Hotspot Access Network(s), the Backbone/Core, etc.) are alsoillustrated. The example network 400 may, for example, share any or allcharacteristics with the other example networks and/or networkcomponents 100, 200, 300, 500-570, 600, 700, 800, 900, and 1000,discussed herein.

The example network 400 shows various mobile networked devices. Suchnetwork devices may comprise end-user devices (e.g., smartphones,tablets, smartwatches, laptop computers, webcams, personal gamingdevices, personal navigation devices, personal media devices, personalcameras, health-monitoring devices, personal location devices,monitoring panels, printers, etc.). Such networked devices may alsocomprise any of a variety of devices operating in the generalenvironment, where such devices might not for example be associated witha particular user (e.g. any or all of the sensor devices discussedherein, vehicle sensors, municipal sensors, fleet sensors road sensors,environmental sensors, security sensors, traffic sensors, waste sensors,meteorological sensors, any of a variety of different types of municipalor enterprise equipment, etc.). Any of such networked devices can beflexibly connected to distinct backbone, fixed hotspot access networks,mobile hotspot access networks, etc., using the same or differentwired/wireless technologies.

A mobile device may, for example, operate as an AP to providesimultaneous access to multiple devices/things, which may then form adhoc networks, interconnecting devices ultimately connected to distinctbackbone networks, fixed hotspot, and/or mobile hotspot access networks.Devices (e.g., any or all of the devices or network nodes discussedherein) may, for example, have redundant technologies to access distinctbackbone, fixed hotspot, and/or mobile hotspot access networks, forexample for fault-tolerance and/or load-balancing purposes (e.g.,utilizing multiple SIM cards, etc.). A device may also, for example,simultaneously access distinct backbone, fixed hotspot access networks,and/or mobile hotspot access networks, belonging to the same provider orto different respective providers. Additionally for example, a devicecan provide multiple accesses to another device/thing (e.g., viadifferent channels, radios, etc.).

Referring back to FIG. 1, the example End-User Devices are shown with awireless communication link to a backbone provider (e.g., to one or moreBackbone Providers and/or Local Infrastructure Providers), to a FixedHotspot Access Network, to a Mobile Hotspot Access Network, and to theEnvironment. Also for example, the example End-User Devices are shownwith a wired communication link to a backbone provider, to a FixedHotspot Access Network, to a Mobile Hotspot Access Network, and to theEnvironment.

The example network 100 illustrated in FIG. 1 has a flexiblearchitecture that is adaptable at implementation time (e.g., fordifferent use cases) and/or adaptable in real-time, for example asnetwork components enter and leave service. FIGS. 5A-5C illustrate suchflexibility by providing example modes (or configurations). The examplenetworks 500-570 may, for example, share any or all characteristics withthe other example networks and/or network components 100, 200, 300, 400,600, 700, 800, 900, and 1000, discussed herein. For example and withoutlimitation, any or all of the communication links (e.g., wired links,wireless links, etc.) shown in the example networks 500-570 aregenerally analogous to similarly positioned communication links shown inthe example network 100 of FIG. 1.

For example, various aspects of this disclosure provide communicationnetwork architectures, systems, and methods for supporting a dynamicallyconfigurable communication network comprising a complex array of bothstatic and moving communication nodes (e.g., the Internet of movingthings). For example, a communication network implemented in accordancewith various aspects of the present disclosure may operate in one of aplurality of modalities comprising various fixed nodes, mobile nodes,and/or a combination thereof, which are selectable to yield any of avariety of system goals (e.g., increased throughput, reduced latency andpacket loss, increased availability and robustness of the system, extraredundancy, increased responsiveness, increased security in thetransmission of data and/or control packets, reduced number ofconfiguration changes by incorporating smart thresholds (e.g., change oftechnology, change of certificate, change of IP, etc.), providingconnectivity in dead zones or zones with difficult access, reducing thecosts for maintenance and accessing the equipment forupdating/upgrading, etc.). At least some of such modalities may, forexample, be entirely comprised of fixed-position nodes, at leasttemporarily if not permanently.

For illustrative simplicity, many of the example aspects shown in theexample system or network 100 of FIG. 1 (and other Figures herein) areomitted from FIGS. 5A-5C, but may be present. For example, the Cloud,Internet, and ISP aspects shown in FIG. 1 and in other Figures are notexplicitly shown in FIGS. 5A-5C, but may be present in any of theexample configurations (e.g., as part of the backbone provider networkor coupled thereto, as part of the local infrastructure provider networkor coupled thereto, etc.).

For example, the first example mode 500 is presented as a normalexecution mode, for example a mode (or configuration) in which all ofthe components discussed herein are present. For example, thecommunication system in the first example mode 500 comprises a backboneprovider network, a local infrastructure provider network, a fixedhotspot access network, a mobile hotspot access network, end-userdevices, and environment devices.

As shown in FIG. 5A, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the first example mode 500 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the localinfrastructure provider network (or any component thereof), fixedhotspot access network (or any component thereof), the end-user devices,and/or environment devices via a wired link. Note that such a wiredcoupling may be temporary. Also note that in various exampleconfigurations, the backbone provider network may also, at leasttemporarily, be communicatively coupled to the mobile hotspot accessnetwork (or any component thereof) via one or more wired (or tethered)links.

Also shown in FIG. 5A, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the first example mode 500 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the fixed hotspot access network (or anycomponent thereof), the mobile hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wireless links. Also note that in various example configurations,the backbone provider network may also be communicatively coupled to thelocal infrastructure provider network via one or more wireless (ornon-tethered) links.

Though not shown in the first example mode 500 (or any of the examplemodes of FIGS. 5A-5C), one or more servers may be communicativelycoupled to the backbone provider network and/or the local infrastructurenetwork. FIG. 1 provides an example of Cloud servers beingcommunicatively coupled to the backbone provider network via theInternet.

As additionally shown in FIG. 5A, and in FIG. 1 in more detail, thelocal infrastructure provider network may be communicatively coupled toany or all of the other elements present in the first example mode 500(or configuration) via one or more wired (or tethered) links. Forexample, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), fixed hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wired links. Note that such a wired coupling may be temporary. Alsonote that in various example configurations, the local infrastructureprovider network may also, at least temporarily, be communicativelycoupled to the mobile hotspot access network (or any component thereof)via one or more wired (or tethered) links.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the first example mode 500 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), the fixed hotspot access network (or any componentthereof), the mobile hotspot access network (or any component thereof),the end-user devices, and/or environment devices via one or morewireless links. Note that the communication link shown in the firstexample mode 500 of FIG. 5A between the local infrastructure providernetwork and the fixed hotspot access network may be wired and/orwireless.

The fixed hotspot access network is also shown in the first example mode500 to be communicatively coupled to the mobile hotspot access network,the end-user devices, and/or environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein. Additionally, the mobile hotspot access network is further shownin the first example mode 500 to be communicatively coupled to theend-user devices and/or environment devices via one or more wirelesslinks. Many examples of such wireless coupling are provided herein.Further, the end-user devices are also shown in the first example mode500 to be communicatively coupled to the environment devices via one ormore wireless links. Many examples of such wireless coupling areprovided herein. Note that in various example implementations any ofsuch wireless links may instead (or in addition) comprise a wired (ortethered) link.

In the first example mode 500 (e.g., the normal mode), information (ordata) may be communicated between an end-user device and a server (e.g.,a computer system) via the mobile hotspot access network, the fixedhotspot access network, the local infrastructure provider network,and/or the backbone provider network. As will be seen in the variousexample modes presented herein, such communication may flexibly occurbetween an end-user device and a server via any of a variety ofdifferent communication pathways, for example depending on theavailability of a network, depending on bandwidth utilization goals,depending on communication priority, depending on communication time (orlatency) and/or reliability constraints, depending on cost, etc. Forexample, information communicated between an end user device and aserver may be communicated via the fixed hotspot access network, thelocal infrastructure provider network, and/or the backbone providernetwork (e.g., skipping the mobile hotspot access network). Also forexample, information communicated between an end user device and aserver may be communicated via the backbone provider network (e.g.,skipping the mobile hotspot access network, fixed hotspot accessnetwork, and/or local infrastructure provider network).

Similarly, in the first example mode 500 (e.g., the normal mode),information (or data) may be communicated between an environment deviceand a server via the mobile hotspot access network, the fixed hotspotaccess network, the local infrastructure provider network, and/or thebackbone provider network. Also for example, an environment device maycommunicate with or through an end-user device (e.g., instead of or inaddition to the mobile hotspot access network). As will be seen in thevarious example modes presented herein, such communication may flexiblyoccur between an environment device and a server (e.g., communicativelycoupled to the local infrastructure provider network and/or backboneprovider network) via any of a variety of different communicationpathways, for example depending on the availability of a network,depending on bandwidth utilization goals, depending on communicationpriority, depending on communication time (or latency) and/orreliability constraints, depending on cost, etc.

For example, information communicated between an environment device anda server may be communicated via the fixed hotspot access network, thelocal infrastructure provider network, and/or the backbone providernetwork (e.g., skipping the mobile hotspot access network). Also forexample, information communicated between an environment device and aserver may be communicated via the backbone provider network (e.g.,skipping the mobile hotspot access network, fixed hotspot accessnetwork, and/or local infrastructure provider network). Additionally forexample, information communicated between an environment device and aserver may be communicated via the local infrastructure provider network(e.g., skipping the mobile hotspot access network and/or fixed hotspotaccess network).

As discussed herein, the example networks presented herein areadaptively configurable to operate in any of a variety of differentmodes (or configurations). Such adaptive configuration may occur atinitial installation and/or during subsequent controlled networkevolution (e.g., adding or removing any or all of the network componentsdiscussed herein, expanding or removing network capacity, adding orremoving coverage areas, adding or removing services, etc.). Suchadaptive configuration may also occur in real-time, for example inresponse to real-time changes in network conditions (e.g., networks orcomponents thereof being available or not based on vehicle oruser-device movement, network or component failure, network or componentreplacement or augmentation activity, network overloading, etc.). Thefollowing example modes are presented to illustrate characteristics ofvarious modes in which a communication system may operate in accordancewith various aspects of the present disclosure. The following examplemodes will generally be discussed in relation to the first example mode500 (e.g., the normal execution mode). Note that such example modes aremerely illustrative and not limiting.

The second example mode (or configuration) 510 (e.g., a no backboneavailable mode) may, for example, share any or all characteristics withthe first example mode 500, albeit without the backbone provider networkand communication links therewith. For example, the communication systemin the second example mode 510 comprises a local infrastructure providernetwork, a fixed hotspot access network, a mobile hotspot accessnetwork, end-user devices, and environment devices.

As shown in FIG. 5A, and in FIG. 1 in more detail, the localinfrastructure provider network may be communicatively coupled to any orall of the other elements present in the second example mode 510 (orconfiguration) via one or more wired (or tethered) links. For example,the local infrastructure provider network may be communicatively coupledto the fixed hotspot access network (or any component thereof), theend-user devices, and/or environment devices via one or more wiredlinks. Note that such a wired coupling may be temporary. Also note thatin various example configurations, the local infrastructure providernetwork may also, at least temporarily, be communicatively coupled tothe mobile hotspot access network (or any component thereof) via one ormore wired (or tethered) links.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the second example mode 510 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the fixed hotspot access network (or anycomponent thereof), the mobile hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wireless links. Note that the communication link(s) shown in thesecond example mode 510 of FIG. 5A between the local infrastructureprovider network and the fixed hotspot access network may be wiredand/or wireless.

The fixed hotspot access network is also shown in the second examplemode 510 to be communicatively coupled to the mobile hotspot accessnetwork, the end-user devices, and/or environment devices via one ormore wireless links. Many examples of such wireless coupling areprovided herein. Additionally, the mobile hotspot access network isfurther shown in the second example mode 510 to be communicativelycoupled to the end-user devices and/or environment devices via one ormore wireless links. Many examples of such wireless coupling areprovided herein. Further, the end-user devices are also shown in thesecond example mode 510 to be communicatively coupled to the environmentdevices via one or more wireless links. Many examples of such wirelesscoupling are provided herein. Note that in various exampleimplementations any of such wireless links may instead (or in addition)comprise a wired (or tethered) link.

In the second example mode 510 (e.g., the no backbone available mode),information (or data) may be communicated between an end-user device anda server (e.g., a computer, etc.) via the mobile hotspot access network,the fixed hotspot access network, and/or the local infrastructureprovider network. As will be seen in the various example modes presentedherein, such communication may flexibly occur between an end-user deviceand a server via any of a variety of different communication pathways,for example depending on the availability of a network, depending onbandwidth utilization goals, depending on communication priority,depending on communication time (or latency) and/or reliabilityconstraints, depending on cost, etc. For example, informationcommunicated between an end user device and a server may be communicatedvia the fixed hotspot access network and/or the local infrastructureprovider network (e.g., skipping the mobile hotspot access network).Also for example, information communicated between an end user deviceand a server may be communicated via the local infrastructure providernetwork (e.g., skipping the mobile hotspot access network and/or fixedhotspot access network).

Similarly, in the second example mode 510 (e.g., the no backboneavailable mode), information (or data) may be communicated between anenvironment device and a server via the mobile hotspot access network,the fixed hotspot access network, and/or the local infrastructureprovider network. Also for example, an environment device maycommunicate with or through an end-user device (e.g., instead of or inaddition to the mobile hotspot access network). As will be seen in thevarious example modes presented herein, such communication may flexiblyoccur between an environment device and a server (e.g., communicativelycoupled to the local infrastructure provider network) via any of avariety of different communication pathways, for example depending onthe availability of a network, depending on bandwidth utilization goals,depending on communication priority, depending on communication time (orlatency) and/or reliability constraints, depending on cost, etc.

For example, information communicated between an environment device anda server may be communicated via the fixed hotspot access network and/orthe local infrastructure provider network (e.g., skipping the mobilehotspot access network). Also for example, information communicatedbetween an environment device and a server may be communicated via thelocal infrastructure provider network (e.g., skipping the mobile hotspotaccess network and/or fixed hotspot access network).

The second example mode 510 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. Forexample, due to security and/or privacy goals, the second example mode510 may be utilized so that communication access to the public Cloudsystems, the Internet in general, etc., is not allowed. For example, allnetwork control and management functions may be within the localinfrastructure provider network (e.g., wired local network, etc.) and/orthe fixed access point network.

In an example implementation, the communication system might be totallyowned, operated and/or controlled by a local port authority. No extraexpenses associated with cellular connections need be spent. Forexample, cellular connection capability (e.g., in Mobile APs, Fixed APs,end user devices, environment devices, etc.) need not be provided. Notealso that the second example mode 510 may be utilized in a scenario inwhich the backbone provider network is normally available but iscurrently unavailable (e.g., due to server failure, due to communicationlink failure, due to power outage, due to a temporary denial of service,etc.).

The third example mode (or configuration) 520 (e.g., a no localinfrastructure and fixed hotspots available mode) may, for example,share any or all characteristics with the first example mode 500, albeitwithout the local infrastructure provider network, the fixed hotspotaccess network, and communication links therewith. For example, thecommunication system in the third example mode 520 comprises a backboneprovider network, a mobile hotspot access network, end-user devices, andenvironment devices.

As shown in FIG. 5A, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the third example mode 520 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the end-user devicesand/or environment devices via one or more wired links. Note that such awired coupling may be temporary. Also note that in various exampleconfigurations, the backbone provider network may also, at leasttemporarily, be communicatively coupled to the mobile hotspot accessnetwork (or any component thereof) via one or more wired (or tethered)links.

Also shown in FIG. 5A, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the third example mode 520 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the mobile hotspot access network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wireless links.

The mobile hotspot access network is further shown in the third examplemode 520 to be communicatively coupled to the end-user devices and/orenvironment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein. Further, the end-userdevices are also shown in the third example mode 520 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein. Note that in various example implementations any of suchwireless links may instead (or in addition) comprise a wired (ortethered) link.

In the third example mode 520 (e.g., the no local infrastructure andfixed hotspots available mode), information (or data) may becommunicated between an end-user device and a server (e.g., a computer,etc.) via the mobile hotspot access network and/or the backbone providernetwork. As will be seen in the various example modes presented herein,such communication may flexibly occur between an end-user device and aserver via any of a variety of different communication pathways, forexample depending on the availability of a network, depending onbandwidth utilization goals, depending on communication priority,depending on communication time (or latency) and/or reliabilityconstraints, depending on cost, etc. For example, informationcommunicated between an end user device and a server may be communicatedvia the backbone provider network (e.g., skipping the mobile hotspotaccess network).

Similarly, in the third example mode 520 (e.g., the no localinfrastructure and fixed hotspots available mode), information (or data)may be communicated between an environment device and a server via themobile hotspot access network and/or the backbone provider network. Alsofor example, an environment device may communicate with or through anend-user device (e.g., instead of or in addition to the mobile hotspotaccess network). As will be seen in the various example modes presentedherein, such communication may flexibly occur between an environmentdevice and a server (e.g., communicatively coupled to the backboneprovider network) via any of a variety of different communicationpathways, for example depending on the availability of a network,depending on bandwidth utilization goals, depending on communicationpriority, depending on communication time (or latency) and/orreliability constraints, depending on cost, etc. For example,information communicated between an environment device and a server maybe communicated via the backbone provider network (e.g., skipping themobile hotspot access network).

In the third example mode 520, all control/management functions may forexample be implemented within the Cloud. For example, since the mobilehotspot access network does not have a communication link via a fixedhotspot access network, the Mobile APs may utilize a direct connection(e.g., a cellular connection) with the backbone provider network (orCloud). If a Mobile AP does not have such capability, the Mobile AP mayalso, for example, utilize data access provided by the end-user devicescommunicatively coupled thereto (e.g., leveraging the data plans of theend-user devices).

The third example mode 520 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation, the third example mode 520 may be utilized in anearly stage of a larger deployment, for example deployment that willgrow into another mode (e.g., the example first mode 500, example fourthmode 530, etc.) as more communication system equipment is installed.Note also that the third example mode 520 may be utilized in a scenarioin which the local infrastructure provider network and fixed hotspotaccess network are normally available but are currently unavailable(e.g., due to equipment failure, due to communication link failure, dueto power outage, due to a temporary denial of service, etc.).

The fourth example mode (or configuration) 530 (e.g., a no fixedhotspots available mode) may, for example, share any or allcharacteristics with the first example mode 500, albeit without thefixed hotspot access network and communication links therewith. Forexample, the communication system in the fourth example mode 530comprises a backbone provider network, a local infrastructure providernetwork, a mobile hotspot access network, end-user devices, andenvironment devices.

As shown in FIG. 5B, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the fourth example mode 530 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the localinfrastructure provider network (or any component thereof), the end-userdevices, and/or environment devices via one or more wired links. Notethat such a wired coupling may be temporary. Also note that in variousexample configurations, the backbone provider network may also, at leasttemporarily, be communicatively coupled to the mobile hotspot accessnetwork (or any component thereof) via one or more wired (or tethered)links.

Also shown in FIG. 5B, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the fourth example mode 530 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the mobile hotspot access network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wireless links. Also note that in various exampleconfigurations, the backbone provider network may also becommunicatively coupled to the local infrastructure provider network viaone or more wireless (or non-tethered) links.

As additionally shown in FIG. 5B, and in FIG. 1 in more detail, thelocal infrastructure provider network may be communicatively coupled toany or all of the other elements present in the fourth example mode 530(or configuration) via one or more wired (or tethered) links. Forexample, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wired links. Note that such a wired coupling may betemporary. Also note that in various example configurations, the localinfrastructure provider network may also, at least temporarily, becommunicatively coupled to the mobile hotspot access network (or anycomponent thereof) via one or more wired (or tethered) links.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the fourth example mode 530 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), the mobile hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wireless links.

The mobile hotspot access network is further shown in the fourth examplemode 530 to be communicatively coupled to the end-user devices and/orenvironment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein. Further, the end-userdevices are also shown in the fourth example mode 530 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein.

In the fourth example mode 530 (e.g., the no fixed hotspots mode),information (or data) may be communicated between an end-user device anda server via the mobile hotspot access network, the local infrastructureprovider network, and/or the backbone provider network. As will be seenin the various example modes presented herein, such communication mayflexibly occur between an end-user device and a server via any of avariety of different communication pathways, for example depending onthe availability of a network, depending on bandwidth utilization goals,depending on communication priority, depending on communication time (orlatency) and/or reliability constraints, depending on cost, etc. Forexample, information communicated between an end user device and aserver may be communicated via the local infrastructure provider networkand/or the backbone provider network (e.g., skipping the mobile hotspotaccess network). Also for example, information communicated between anend user device and a server may be communicated via the backboneprovider network (e.g., skipping the mobile hotspot access networkand/or local infrastructure provider network).

Similarly, in the fourth example mode 530 (e.g., the no fixed hotspotsavailable mode), information (or data) may be communicated between anenvironment device and a server via the mobile hotspot access network,the local infrastructure provider network, and/or the backbone providernetwork. Also for example, an environment device may communicate with orthrough an end-user device (e.g., instead of or in addition to themobile hotspot access network). As will be seen in the various examplemodes presented herein, such communication may flexibly occur between anenvironment device and a server (e.g., communicatively coupled to thelocal infrastructure provider network and/or backbone provider network)via any of a variety of different communication pathways, for exampledepending on the availability of a network, depending on bandwidthutilization goals, depending on communication priority, depending oncommunication time (or latency) and/or reliability constraints,depending on cost, etc.

For example, information communicated between an environment device anda server may be communicated via the local infrastructure providernetwork and/or the backbone provider network (e.g., skipping the mobilehotspot access network). Also for example, information communicatedbetween an environment device and a server may be communicated via thebackbone provider network (e.g., skipping the mobile hotspot accessnetwork and/or local infrastructure provider network). Additionally forexample, information communicated between an environment device and aserver may be communicated via the local infrastructure provider network(e.g., skipping the mobile hotspot access network and/or backboneprovider network).

In the fourth example mode 530, in an example implementation, some ofthe control/management functions may for example be implemented withinthe local backbone provider network (e.g., within a client premises).For example, communication to the local infrastructure provider may beperformed through the backbone provider network (or Cloud). Note that ina scenario in which there is a direct communication pathway between thelocal infrastructure provider network and the mobile hotspot accessnetwork, such communication pathway may be utilized.

For example, since the mobile hotspot access network does not have acommunication link via a fixed hotspot access network, the Mobile APsmay utilize a direct connection (e.g., a cellular connection) with thebackbone provider network (or Cloud). If a Mobile AP does not have suchcapability, the Mobile AP may also, for example, utilize data accessprovided by the end-user devices communicatively coupled thereto (e.g.,leveraging the data plans of the end-user devices).

The fourth example mode 530 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation, the fourth example mode 530 may be utilized inan early stage of a larger deployment, for example a deployment thatwill grow into another mode (e.g., the example first mode 500, etc.) asmore communication system equipment is installed. The fourth examplemode 530 may, for example, be utilized in a scenario in which there isno fiber (or other) connection available for Fixed APs (e.g., in amaritime scenario, in a plantation scenario, etc.), or in which a FixedAP is difficult to access or connect. For example, one or more MobileAPs of the mobile hotspot access network may be used as gateways toreach the Cloud. The fourth example mode 530 may also, for example, beutilized when a vehicle fleet and/or the Mobile APs associated therewithare owned by a first entity and the Fixed APs are owned by anotherentity, and there is no present agreement for communication between theMobile APs and the Fixed APs. Note also that the fourth example mode 530may be utilized in a scenario in which the fixed hotspot access networkis normally available but are currently unavailable (e.g., due toequipment failure, due to communication link failure, due to poweroutage, due to a temporary denial of service, etc.).

The fifth example mode (or configuration) 540 (e.g., a no mobilehotspots available mode) may, for example, share any or allcharacteristics with the first example mode 500, albeit without themobile hotspot access network and communication links therewith. Forexample, the communication system in the fifth example mode 540comprises a backbone provider network, a local infrastructure providernetwork, a fixed hotspot access network, end-user devices, andenvironment devices.

As shown in FIG. 5B, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the fifth example mode 540 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the localinfrastructure provider network (or any component thereof), fixedhotspot access network (or any component thereof), the end-user devices,and/or environment devices via one or more wired links. Note that such awired coupling may be temporary.

Also shown in FIG. 5B, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the fifth example mode 540 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the fixed hotspot access network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wireless links. Also note that in various exampleconfigurations, the backbone provider network may also becommunicatively coupled to the local infrastructure provider network viaone or more wireless (or non-tethered) links.

As additionally shown in FIG. 5B, and in FIG. 1 in more detail, thelocal infrastructure provider network may be communicatively coupled toany or all of the other elements present in the fifth example mode 540(or configuration) via one or more wired (or tethered) links. Forexample, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), fixed hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wired links. Note that such a wired coupling may be temporary. Alsonote that in various example configurations, the local infrastructureprovider network may also, at least temporarily, be communicativelycoupled to the mobile hotspot access network (or any component thereof)via one or more wired (or tethered) links.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the fifth example mode 540 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the backbone provider network, the fixedhotspot access network (or any component thereof), the end-user devices,and/or environment devices via one or more wireless links. Note that thecommunication link(s) shown in the fifth example mode 540 of FIG. 5Bbetween the local infrastructure provider network and the fixed hotspotaccess network may be wired and/or wireless.

The fixed hotspot access network is also shown in the fifth example mode540 to be communicatively coupled to the end-user devices and/orenvironment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein. Further, the end-userdevices are also shown in the fifth example mode 540 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein.

In the fifth example mode 540 (e.g., the no mobile hotspots availablemode), information (or data) may be communicated between an end-userdevice and a server via the fixed hotspot access network, the localinfrastructure provider network, and/or the backbone provider network.As will be seen in the various example modes presented herein, suchcommunication may flexibly occur between an end-user device and a servervia any of a variety of different communication pathways, for exampledepending on the availability of a network, depending on bandwidthutilization goals, depending on communication priority, depending oncommunication time (or latency) and/or reliability constraints,depending on cost, etc. For example, information communicated between anend user device and a server may be communicated via the localinfrastructure provider network, and/or the backbone provider network(e.g., skipping the fixed hotspot access network). Also for example,information communicated between an end user device and a server may becommunicated via the backbone provider network (e.g., skipping the fixedhotspot access network and/or local infrastructure provider network).

Similarly, in the fifth example mode 540 (e.g., the no mobile hotspotsavailable mode), information (or data) may be communicated between anenvironment device and a server via the fixed hotspot access network,the local infrastructure provider network, and/or the backbone providernetwork. Also for example, an environment device may communicate with orthrough an end-user device (e.g., instead of or in addition to the fixedhotspot access network). As will be seen in the various example modespresented herein, such communication may flexibly occur between anenvironment device and a server (e.g., communicatively coupled to thelocal infrastructure provider network and/or backbone provider network)via any of a variety of different communication pathways, for exampledepending on the availability of a network, depending on bandwidthutilization goals, depending on communication priority, depending oncommunication time (or latency) and/or reliability constraints,depending on cost, etc.

For example, information communicated between an environment device anda server may be communicated via the local infrastructure providernetwork and/or the backbone provider network (e.g., skipping the fixedhotspot access network). Also for example, information communicatedbetween an environment device and a server may be communicated via thebackbone provider network (e.g., skipping the fixed hotspot accessnetwork and/or local infrastructure provider network). Additionally forexample, information communicated between an environment device and aserver may be communicated via the local infrastructure provider network(e.g., skipping the fixed hotspot access network and/or the backboneprovider network).

In the fifth example mode 540, in an example implementation, theend-user devices and environment devices may communicate directly toFixed APs (e.g., utilizing Ethernet, Wi-Fi, etc.). Also for example, theend-user devices and/or environment devices may communicate directlywith the backbone provider network (e.g., utilizing cellularconnections, etc.).

The fifth example mode 540 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation in which end-user devices and/or environmentdevices may communicate directly with Fixed APs, such communication maybe utilized instead of Mobile AP communication. For example, the fixedhotspot access network might provide coverage for all desired areas.

Note also that the fifth example mode 540 may be utilized in a scenarioin which the fixed hotspot access network is normally available but iscurrently unavailable (e.g., due to equipment failure, due tocommunication link failure, due to power outage, due to a temporarydenial of service, etc.).

The sixth example mode (or configuration) 550 (e.g., the no fixed/mobilehotspots and local infrastructure available mode) may, for example,share any or all characteristics with the first example mode 500, albeitwithout the local infrastructure provider network, fixed hotspot accessnetwork, mobile hotspot access network, and communication linkstherewith. For example, the communication system in the sixth examplemode 550 comprises a backbone provider network, end-user devices, andenvironment devices.

As shown in FIG. 5B, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the sixth example mode 550 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the end-user devicesand/or environment devices via one or more wired links. Note that such awired coupling may be temporary.

Also shown in FIG. 5B, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the sixth example mode 550 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the end-user devices and/or environmentdevices via one or more wireless links.

The end-user devices are also shown in the sixth example mode 550 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein.

In the sixth example mode 550 (e.g., the no fixed/mobile hotspots andlocal infrastructure available mode), information (or data) may becommunicated between an end-user device and a server via the backboneprovider network. Similarly, in the sixth example mode 550 (e.g., the nofixed/mobile hotspots and local infrastructure mode), information (ordata) may be communicated between an environment device and a server viathe backbone provider network. Also for example, an environment devicemay communicate with or through an end-user device (e.g., instead of orin addition to the mobile hotspot access network).

The sixth example mode 550 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation, for example in which an end-user has not yetsubscribed to the communication system, the end-user device maysubscribe to the system through a Cloud application and by communicatingdirectly with the backbone provider network (e.g., via cellular link,etc.). The sixth example mode 550 may also, for example, be utilized inrural areas in which Mobile AP presence is sparse, Fixed AP installationis difficult or impractical, etc.

Note also that the sixth example mode 550 may be utilized in a scenarioin which the infrastructure provider network, fixed hotspot accessnetwork, and/or mobile hotspot access network are normally available butare currently unavailable (e.g., due to equipment failure, due tocommunication link failure, due to power outage, due to a temporarydenial of service, etc.).

The seventh example mode (or configuration) 560 (e.g., the no backboneand mobile hotspots available mode) may, for example, share any or allcharacteristics with the first example mode 500, albeit without thebackbone provider network, mobile hotspot access network, andcommunication links therewith. For example, the communication system inthe seventh example mode 560 comprises a local infrastructure providernetwork, fixed hotspot access network, end-user devices, and environmentdevices.

As shown in FIG. 5C, and in FIG. 1 in more detail, the localinfrastructure provider network may be communicatively coupled to any orall of the other elements present in the seventh example mode 560 (orconfiguration) via one or more wired (or tethered) links. For example,the local infrastructure provider network may be communicatively coupledto the fixed hotspot access network (or any component thereof), theend-user devices, and/or environment devices via one or more wiredlinks. Note that such a wired coupling may be temporary.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the seventh example mode 560 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the fixed hotspot access network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wireless links. Note that the communication link shown inthe seventh example mode 560 of FIG. 5C between the local infrastructureprovider network and the fixed hotspot access network may be wiredand/or wireless.

The fixed hotspot access network is also shown in the seventh examplemode 560 to be communicatively coupled to the end-user devices and/orenvironment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein. Additionally, the end-userdevices are also shown in the seventh example mode 560 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein.

In the seventh example mode 560 (e.g., the no backbone and mobilehotspots available mode), information (or data) may be communicatedbetween an end-user device and a server via the fixed hotspot accessnetwork and/or the local infrastructure provider network. As will beseen in the various example modes presented herein, such communicationmay flexibly occur between an end-user device and a server via any of avariety of different communication pathways, for example depending onthe availability of a network, depending on bandwidth utilization goals,depending on communication priority, depending on communication time (orlatency) and/or reliability constraints, depending on cost, etc. Forexample, information communicated between an end user device and aserver may be communicated via the local infrastructure provider network(e.g., skipping the fixed hotspot access network).

Similarly, in the seventh example mode 560 (e.g., the no backbone andmobile hotspots available mode), information (or data) may becommunicated between an environment device and a server via the fixedhotspot access network and/or the local infrastructure provider network.Also for example, an environment device may communicate with or throughan end-user device (e.g., instead of or in addition to the mobilehotspot access network). As will be seen in the various example modespresented herein, such communication may flexibly occur between anenvironment device and a server (e.g., communicatively coupled to thelocal infrastructure provider network) via any of a variety of differentcommunication pathways, for example depending on the availability of anetwork, depending on bandwidth utilization goals, depending oncommunication priority, depending on communication time (or latency)and/or reliability constraints, depending on cost, etc. For example,information communicated between an environment device and a server maybe communicated via the local infrastructure provider network (e.g.,skipping the fixed hotspot access network).

The seventh example mode 560 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample controlled space implementation, Cloud access might not beprovided (e.g., for security reasons, privacy reasons, etc.), and full(or sufficient) coverage of the coverage area is provided by the fixedhotspot access network, and thus the mobile hotspot access network isnot needed. For example, the end-user devices and environment devicesmay communicate directly (e.g., via Ethernet, Wi-Fi, etc.) with theFixed APs

Note also that the seventh example mode 560 may be utilized in ascenario in which the backbone provider network and/or fixed hotspotaccess network are normally available but are currently unavailable(e.g., due to equipment failure, due to communication link failure, dueto power outage, due to a temporary denial of service, etc.).

The eighth example mode (or configuration) 570 (e.g., the no backbone,fixed hotspots, and local infrastructure available mode) may, forexample, share any or all characteristics with the first example mode500, albeit without the backbone provider network, local infrastructureprovider network, fixed hotspot access network, and communication linkstherewith. For example, the communication system in the eighth examplemode 570 comprises a mobile hotspot access network, end-user devices,and environment devices.

As shown in FIG. 5C, and in FIG. 1 in more detail, the mobile hotspotaccess network is shown in the eighth example mode 570 to becommunicatively coupled to the end-user devices and/or environmentdevices via one or more wireless links. Many examples of such wirelesscoupling are provided herein. Further, the end-user devices are alsoshown in the eighth example mode 570 to be communicatively coupled tothe environment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein.

In the eighth example mode 570 (e.g., the no backbone, fixed hotspots,and local infrastructure available mode), information (or data) mightnot (at least currently) be communicated between an end-user device anda server (e.g., a coupled to the backbone provider network, localinfrastructure provider network, etc.). Similarly, information (or data)might not (at least currently) be communicated between an environmentdevice and a server (e.g., a coupled to the backbone provider network,local infrastructure provider network, etc.). Note that the environmentdevice may communicate with or through an end-user device (e.g., insteadof or in addition to the mobile hotspot access network).

The eighth example mode 570 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation, the eighth example mode 570 may be utilized forgathering and/or serving data (e.g., in a delay-tolerant networkingscenario), providing peer-to-peer communication through the mobilehotspot access network (e.g., between clients of a single Mobile AP,between clients of respective different Mobile APs, etc.), etc. Inanother example scenario, the eighth example mode 570 may be utilized ina scenario in which vehicle-to-vehicle communications are prioritizedabove vehicle-to-infrastructure communications. In yet another examplescenario, the eighth example mode 570 may be utilized in a scenario inwhich all infrastructure access is lost (e.g., in tunnels, parkinggarages, etc.).

Note also that the eighth example mode 570 may be utilized in a scenarioin which the backbone provider network, local infrastructure providernetwork, and/or fixed hotspot access network are normally available butare currently unavailable (e.g., due to equipment failure, due tocommunication link failure, due to power outage, due to a temporarydenial of service, etc.).

As shown and discussed herein, it is beneficial to have a genericplatform that allows multi-mode communications of multiple users ormachines within different environments, using multiple devices withmultiple technologies, connected to multiple moving/static things withmultiple technologies, forming wireless (mesh) hotspot networks overdifferent environments, connected to multiple wired/wirelessinfrastructure/network backbone providers, ultimately connected to theInternet, Cloud or private network infrastructure.

FIG. 6 shows yet another block diagram of an example networkconfiguration, in accordance with various aspects of the presentdisclosure. The example network 600 may, for example, share any or allcharacteristics with the other example networks and/or networkcomponents 100, 200, 300, 400, 500-570, 700, 800, 900, and 1000,discussed herein. Notably, the example network 600 shows a plurality ofMobile APs (or OBUs), each communicatively coupled to a Fixed AP (orRSU), where each Mobile AP may provide network access to a vehiclenetwork (e.g., comprising other vehicles or vehicle networks, userdevices, sensor devices, etc.).

As shown in the various example communication networks presented herein,a Mobile AP may establish a communication link with the backbone (orbackhaul) network in any of a variety of manners. Various aspects of thepresent disclosure provide systems and methods for managing theconnectivity between various nodes. Most examples herein are presentedin the context of managing connectivity between Mobile APs and thebackhaul, but the scope of this disclosure is not limited thereto. Forexample, any or all aspects of the present disclosure may be applied toFixed APs and/or other communication network nodes.

Various aspects of the present disclosure provide a vehicle network(e.g., a smart city network, a harbor network, a port network, a campusnetwork, etc.) that provides continuous connectivity, for examplebetween an end user (or client) device or sensor and a backhaul (orbackbone) network. The topology of a vehicle-based communicationnetwork, for example including Mobile APs, may change rapidly, often,and in unexpected manners. Thus, the various connections, for examplebetween a Mobile AP and the backhaul network may need to be updatedquickly and often. Additionally, the possibility of misconfiguration,malfunction, malicious attacks, etc. may render various portions of thenetwork unusable, for example causing Mobile or Fixed APs to fail toprovide access to the backhaul network (e.g., despite advertising suchaccess). Further, in various use scenarios (e.g., for security reasons,for performance reasons, etc.), some nodes might not be allowed toconnect to particular APs and/or might only be allowed to connect to arestricted set of APs. Still further, because Fixed APs might not coverthe entire geographical region of operation (e.g., due to cost orinstallation issues, outages, etc.), alternative connection technologiesmay be utilized for a node (e.g., fallback connection technologies), forexample a connection technology that is widely available within theregion. Additionally, various applications (e.g., IP mobility, etc.) mayleverage some degree of control over the connection, for example tovalidate the connection, perform auxiliary tasks when a connection isestablished, etc. Also, in various operating scenarios (e.g., LoS(Line-of-Sight), NLoS (Non-Line-of-Sight), etc.), for example operationin tunnels, on or under bridges, at crossroads, in container or storagecanyons in ports, etc., various communication technologies may haveadvantages over other communication technologies (e.g., DSRC over Wi-Fi,etc.). Further, certain APs may use dedicated technologies and/or aplurality of technologies that may be flexibly selected and utilized(e.g., IEEE 802.11p, 802.11a/b/g/n, etc.), sometimes even differenttechnologies within a same network.

Accordingly, various aspects of the present disclosure provide an entity(e.g., an independent, dedicated entity, etc.) that decides how toconnect to the backhaul network, establishes the connection, andmonitors an existing connection for failures. The entity may, forexample, be referred to herein in a non-limiting manner as a “ConnectionManagement Entity” or CME. An example of the CME 710 is provided in FIG.7, which shows a block diagram of an example connection managementsystem of a communication network, in accordance with various aspects ofthe present disclosure. For example and without limitation, any or allof the various components of the example system 700 may be implementedin a Mobile AP. The example system 700 may, for example, share any orall characteristics with the other example networks and/or networkcomponents 100, 200, 300, 400, 500-570, 600, 800, 900, and 1000,discussed herein.

The CME 710 (e.g., a module, a process, etc.) may, for example, beimplemented in a Mobile AP. The CME 710 or any portion thereof may also,however, be implemented in any of a variety of nodes (e.g., a Fixed AP,etc.) or may be implemented in a distributed manner between variousnodes. The CME 710 may, for example, keep track of neighboring nodesavailable for connection and/or broadcast the current node's ownavailability. The CME 710 may, for example, support multi-hopconnections to other nodes (e.g., a Mobile AP connecting to anotherMobile AP, which is in turn connected to a Fixed AP, etc.) and/or serveas a routing (or intermediate) node for neighbors (e.g.,simultaneously). The CME 710 may, for example, support multipleconnection technologies with variable decision weights and costfunctions, handling scenarios with different levels of mobility anddensity of nodes in an adaptive and configurable fashion. The CME 710may, for example, utilize a fallback technology, such as a cellular orsatellite network, to provide connectivity in areas where there is noFixed or Mobile AP coverage. Such technology may also be utilized inemergency scenarios (e.g., when a relatively more expensive butrelatively more reliable cellular network may be utilized instead ofother available networks). The CME 710 may also, for example, providehooks (or interfaces) for external entities to control certain aspectsof the connection, to adapt the cost function or other nodedecision-making criteria, etc. The CME 710 may also, for example,maintain a blacklist of APs that are not to be utilized (e.g., APs thatadvertise a backhaul connection but that do not provide it, etc.),and/or maintain a whitelist of APs that may be utilized (e.g., arestricted set of APs that may be connected to).

In accordance with various aspects of this disclosure, a cost functionH(*) may be provided, for example to be minimized by the ConnectionManagement Entity (CME) 710 when performing a decision. The costfunction may comprise any of a variety of characteristics, non-limitingexamples of which are provided herein. For example, the cost functionmay be based on a single parameter and/or a plurality of parameters(e.g., a weighted function in which various parameters may be weighteddifferently or equally). An example cost function may, for example,consider any one or more of: a Received Signal Strength Indicator (RSSI)(or negative thereof) of the link to the candidate node; an average ofthe RSSI (or negative thereof) over the uplink chain of the candidatenode; the geographical distance to the candidate node, the velocity ofthe candidate node (e.g., relative to the CME's node or in absoluteterms), whether the candidate node is stopped, relatively slow moving,or relatively fast moving, etc.); the type of the candidate node (e.g.,mobile or fixed, etc.); the present load of the candidate node,preferences of users that are connected to the AP (e.g., specifyingpreferred nodes or nodes types, forbidden nodes or node types,authorized nodes or node types, etc.), etc. A stationary or slow-movingnode may, for example, be preferred over fast-moving nodes. A nodeserving relatively few other nodes may, for example, be preferred over anode serving many other nodes. Location, velocity, and/or trajectory maybe utilized to estimate an amount of time for which a node may bein-range, where a node having a velocity indicative of a longer in-rangetime may be preferred. Also for example, route information for a vehiclemay be utilized to identify a node that will be within range for thelongest expected time. Further for example, historical data regardingrepeating connections may be utilized to tune the selection process.Such historical data may, for example, be retrieved or indexed bygeographical location of the node. For example, the cost function mayconsider any information from the Neighbor Information Base (NIB)discussed herein. The cost function may also be configurable, forexample redefined dynamically based on the client requirements, thepresent needs of a fleet, present operating conditions, present monetarycosts, present loads, present emergency or other prioritizationconditions, present delay tolerance conditions, etc.

Note that the node selection function may be expanded to includeinformation from other nodes regarding connectivity and/or throughputissues detected in real-time by the other nodes. For example, anothernode may provide information concerning detected network bottlenecks,cut-offs, security issues, etc. Also note that node priority may beconsidered in the node selection.

A Neighbor Information Base (NIB) 704 may be provided, which storesinformation about neighboring nodes (NN) and makes such informationavailable to other entities in the system. The information about each NNmay also be referred to herein as its context. The context may comprise,for example for each NN, enough information to connect to it and/or todetermine whether to connect to it. The context may, for example andwithout limitation, comprise:

-   -   a. a node identifier (NID);    -   b. the type of node (e.g., fixed, mobile, etc.);    -   c. the type of its backhaul connection;    -   d. the state of its backhaul connection (e.g., one of: NONE,        ONGOING, ESTABLISHED, etc.);    -   e. the number of hops used for the backhaul connection;    -   f. the NID of the node to which it is connected, if applicable;        and    -   g. the NID of the endpoint of its backhaul connection, if        applicable.

The context may also, for example, include all other information,various examples of which are presented herein, that may be utilized tocalculate the cost function H(*) and/or to generally select a node withwhich to connect. Note that the NIB 704 or a portion thereof may bestored and/or maintained locally with the CME 710 (e.g., within a samenode), and/or the NIB 704 may be stored and/or maintained remote fromthe CME 710 (e.g., within a different node, within a Cloud server,etc.).

In accordance with various aspects of this disclosure, a CHannelManagement Entity (CHME) 705 is provided, which advertises informationabout the node to the NNs, for example using any of a variety oftechnologies (e.g., 802.11p WAVE services, dual Wi-Fi radios with oneradio configured as the AP, etc.). The information transmitted by theCHME 705 may, for example, comprise the types of information that arestored in each NIB entry.

The CME 710 may, for example, perform various types of functionality.For example, the CME 710 may perform connection functionality, forexample establishing one or more connections to the backhaul network,which is illustrated as the Connection block 701 in FIG. 7; Decisionfunctionality, for example deciding what network(s) the node is to use,which is illustrated as the Decision block 702 in FIG. 7; and Monitoringfunctionality 703, for example monitoring the existing connection(s) forfailures, anomalies, various performance metrics, etc., which isillustrated as the Monitoring block 703 in FIG. 7. The CME 710 (e.g.,the operation thereof) may be configured utilizing any of a variety ofparameters, non-limiting examples of which are provided herein. Suchparameters may, for example, comprise:

Parameter Symbol Maximum length of uplink chain U_(max) Maximum numberof retries for each NN R_(max) Maximum time to keep an NN in thedecision blacklist T_(bl) NN blacklist for decision L_(b) NN whitelistfor decision L_(w) Decision cycle period T_(d) Monitor cycle periodT_(m) Maximum time for disconnection to finish T_(x) Maximum time untilNN is considered to have disappeared T_(l) Minimum time to consider NNviable for decision T_(OK) Minimum time to change NN decision T_(sw)Minimum difference in cost function value to switch decision ΔH_(min)

The example Connection block 701 may, for example, receive (or retrieve)information from the Decision block 702 in order to establish a newconnection (e.g., a new connection to an AP or fallback network). In oneexample implementation, the Connection block 701 may:

-   -   1. Notify the Monitor block 703 that a connection will take        place.    -   2. Request that the CHME 705 advertise the ONGOING connection.    -   3. Invoke each External Connection Entity (ECE) 706 in a        predefined order. Each ECE 706 may for example perform such        tasks as: preemptively testing the new connection (e.g., by        attempting to reach the backhaul network or specific hosts, by        performing handshakes with control servers, etc.), setting up IP        mobility, establishing network routes, etc. Any ECE 706 may for        example interrupt the connection process if necessary.    -   4. Request that the CHME 705 advertise the ESTABLISHED        connection.    -   5. Notify the Decision block 702 and the Monitor block 703 of        the new connection.

In an example scenario in which there is a failure in any of the abovesteps or an interruption by an ECE 706, the Decision block 702 and theMonitor block 703 are notified of the failure and the CME 710 requeststhat the CHME 705 advertise the NONE connection state. Apart fromestablishing connections, the Connection block 701 may also beresponsible for disconnecting from the backhaul whenever the Decisionblock 702 so decides.

The example Decision block 702 may, for example, make decisions aboutthe preferred backhaul connection(s) and communicate them to theConnection block 701. The Decision block 702 may, for example, maintaina list of NNs, for example a Candidate Neighbor List (CNL). Each entryin the CNL may, for example, comprise any of a variety of differenttypes of information, non-limiting examples of which are providedherein. For example, where each node entry in the CNL may comprise:

Field Symbol Flag indicating whether it is valid to connect to this nodeCN_(OK) Number of times a connection to this node was attempted CN_(att)Time elapsed since node was first added to the CNL CN₀ Time elapsedsince node was last obtained from the NIB CN_(l) Time elapsed since nodeminimized cost function CN_(opt) Time elapsed since node was temporarilyblacklisted CN_(bl) Context of node obtained from NIB —

In order to maintain the CNL (or information thereof), the Decisionblock 702 may, for example, perform the following procedure eitherperiodically (e.g., with period T_(d)), whenever the NIB 704 alerts theDecision block 702 of changes to the NID table, whenever the NIB 704advertises the NID table or portions thereof (e.g., periodically whetheror not the NID table has been changed, etc.), etc.:

-   -   1. Obtain the information for all of the NNs from the NIB 704,        ignoring: unconnected nodes; nodes with long uplink chains        (≥U_(max)); nodes ∈L_(b), if the list exists; and nodes ∉L_(w),        if the list exists. All NNs which are not ignored are termed        Candidate Nodes (CN).    -   2. For all CNs already in the CNL:        -   a. If the number of hops used for the backhaul connection,            the next hop in the uplink chain, or the connection endpoint            change, reset the retry counter (CN_(att)←0).        -   b. If the CN_(att)≥R_(max):            -   i. If CN_(OK) is set, unset it and set CN_(bl) to the                current time.            -   ii. Else, if CN_(bl)≥T_(bl), CN_(att)←0 and CN_(OK) is                set.        -   c. Else, if CN_(OK) is not set and CN₀≥T_(OK), set CN_(OK).    -   3. For all CNs not yet in the CNL, add the CN to the CNL.

The CNL may, for example, then be pruned (or filtered) by removing allCNs where CN_(l)≥T_(l). For all CNs in the CNL with CN_(OK) set, the onewhich minimizes H(*) may be picked as the Optimal Node (ON). If no validCN is available but a fallback network exists and may be used, suchfallback network is picked as the preferred connection method. If nofallback network exists, then the Decision block 702 informs theConnection block 701 that no connection is currently possible.

If a fallback network is currently in use, the ON is immediately pickedas the node to use for the backhaul connection; otherwise, if there is acurrent connection through an Established Node (EN), the ON is onlypicked if H(EN)−H(ON)≥ΔH_(min) and ON_(opt)≥T_(sw), in which case itbecomes the EN. Once a new decision is made, the Decision block 702informs the Connection block 701, and the Decision block 702 expects aresponse indicating the success or failure of the connection. If an ENexists and the connection fails, EN_(att) is incremented.

The Monitor block 703 may, for example, verify the connection state. Forexample, the Monitor block 703 may periodically (e.g., with periodT_(m)) or continually verify the connection state so long as there is anactive connection, as informed by the Connection block 701. To do so,the Monitor block 703 may, for example, invoke one or more ExternalMonitor Entities (EME) 707, which check for failures or relevant changesin any of the components managed by the ECEs 706 (e.g., network routes,network interface addresses, etc.) and report them to Monitor block 703,which in turn informs the Connection block 701 (e.g., for connectionrepair). Additionally, the Monitor block 703 may also keep track of thecontext of the next hop node, if applicable, and inform the Connectionblock 701 any time its connection status changes (e.g., the length ofits uplink chain, its own next hop, the connection endpoint, etc.).Additionally for example, once the Monitor block 703 is informed thatthe connection will be undone (or broken down), it may wait (e.g., up toT_(x)) for the EMEs 707 to report that the disconnection was properlyperformed and for the CHME 705 to advertise the NONE connection state.

As shown here, the CME 710 (and/or related modules) provides a generalmechanism to manage connections (e.g., backhaul connections, etc.) invery dynamic, fast-changing, heterogeneous networks. The connectionmanagement system and/or method provided herein also supports arbitraryexternal entities to control various aspects of the connection,supplying a high-performance and integrated replacement for ad-hocsolutions, which simplifies the implementation of solutions like IPmobility. The dynamic topology of vehicular networks no longer causes(or causes fewer) connectivity issues, for example due to the responsivearchitecture of the CME 710 and the use of a Monitor block 703. Also,the use of a generic CHME 705 and cost function allows the adaptation ofthe decision to multiple technologies, supporting heterogeneous networkswith fallback. Further, multi-hop connections are entirely supported. Inaddition, various security concerns are addressed by supporting(possibly dynamic) AP whitelists and blacklists, which may be used notonly for testing purposes but also to partition the network (e.g., froma central management entity).

A communication network (or components thereof) implemented inaccordance with various aspects of this disclosure facilitates use caseswith Wi-Fi-on-the-move and ground team management, for example byimplementing always-on backhaul connection, including to the Internetand/or private networks, in cities and difficult spaces with radioobstructions or low AP density, for example through the use of multi-hopconnectivity. Such a network (or components thereof) also simplifies theimplementation of added-value services (e.g., including dynamic networkreconfiguration, software updates, etc.), including third-party, byallowing the use of a normal IP-based protocol stack and remote serversin public or private clouds. The use of a variable (or adaptable) costfunction allows clients and operators to determine cost/performancetrade-offs, for example minimizing traffic usage costs by avoidingfallback networks which are typically more expensive.

As discussed herein, any of a variety of technologies may be utilized toestablish a communication link between a Mobile AP and the backhaul (orbackbone) network, the cloud, etc. In an example implementation, one ofthe selectable links (or link technologies) may comprise Wi-Fi. Forexample, in various networking environments, for example urbanenvironments, Wi-Fi hotspots are widely deployed in public locations(e.g., parks, coffee shops, restaurants, bars, stores, malls, publicservice, transportation hubs, etc.). Moreover, many of such hotspots (orportions thereof) do not require authentication. Additionally, telcooperators are deploying their own networks of Wi-Fi hotspots, forexample to provide more and better connectivity to their customers, andto also facilitate offloading traffic from their cellular networks.Additionally, residential gateways may also be equipped with bothprivate and public Wi-Fi networks, which for example allow customers ofa telco operator to use the public Wi-Fi network provided by thegateways of other customers.

The proliferation of Wi-Fi hotspots offers a cost-effective opportunityfor both mobile and Fixed APs to connect to the Internet as a backhaulof the network of moving things. For example, reliable Wi-Fi hotspotswith a good signal quality can be identified in order to provide theinfrastructure backbone to Fixed APs, avoiding the necessity ofdeploying the expensive cable connectivity (e.g., fiber, etc.). SuchWi-Fi hotspots can also be used to perform bidirectional content offload(e.g., to and from the Mobile APs), which, depending on their density,reduces the costs of deploying a network of moving thingsinfrastructure.

Various aspects of the present invention thus provide for Wi-Ficonnectivity to the Internet, for both Fixed APs and Mobile APs. Aconnection manager (e.g., a CME) may, for example, look for Wi-Ficonnectivity opportunities in addition to connectivity opportunitiesbetween Mobile APs and Fixed APs (or, for example, cellular connectivityopportunities). A Wi-Fi connectivity survey mechanism may, for example,maintain a database of preferred and/or useful Wi-Fi hotspots (e.g.,containing location information, identification information, accessinformation if needed, etc.).

FIG. 8 shows a block diagram of an example communication network, inaccordance with various aspects of the present disclosure. The examplenetwork 800 may, for example, share any or all characteristics with theother example networks and/or network components 100, 200, 300, 400,500-570, 600, 700, 900, and 1000 discussed herein.

The example network 800 illustrates various example scenarios utilizingWi-Fi for backhaul functionality or connectivity. In a first examplescenario, a first Mobile AP 811 may connect to the public Wi-Fi networkprovided by a residential gateway 831. For example, a residence maycomprise a Wi-Fi hotspot partitioned for private access (e.g., for theinhabitants of the residence) and for public access. Such partitioningmay, for example, be implemented with different respective Wi-Fitransceivers operating in different bands or on different channels. Inanother example scenario, a second Mobile AP 812 may connect directly toa second public (or proprietary with permission) outdoor Wi-Fi hotspot832. In turn, a third Mobile AP 813 connects via DSRC to the secondMobile AP 812 to reach the Internet (or Cloud). The third Wi-Fi hotspot833 (e.g., at a shop, restaurant, store, pub, etc.) can also be used asbackhaul for a Fixed AP 821, which in turn provides connectivity to afourth Mobile AP 814 via DSRC. Such a configuration may, for example,facilitate relatively easy installment of Fixed AP service, for examplepermanently or temporarily (e.g., until wired connections areestablished to the Fixed

AP.

As shown in FIG. 8 and as discussed herein, both Mobile and Fixed APsmay be equipped with a Wi-Fi network interface dedicated to searchingfor Wi-Fi connection opportunities and/or maintaining Wi-Fi links (e.g.,infrastructure links). This may, for example, be implemented utilizingmulti-radio Wi-Fi technology in which a first Wi-Fi transceiver (e.g.,of a Mobile AP) is utilized to provide connectivity to end user clients,sensors, etc., and a second Wi-Fi transceiver is utilized to search forand/or provide backbone connectivity with a Wi-Fi hotspot whenavailable. For example, the first Wi-Fi transceiver may operate indifferent frequency bands (e.g., 2.4 GHz and 5 GHz) and/or differentchannels within the same band.

When moving, the Mobile AP may be able to associate with different Wi-Fihotspots as the Mobile AP moves in-range and out-of-range of suchhotspots. For a Fixed AP, the AP may typically be associated to onereliable Wi-Fi network or hotspot (and for example a second Wi-Finetwork or hotspot as a fail-over network).

The Mobile AP may, for example, execute an algorithm that controls whichWi-Fi hotspots it should associate with and, if it is successful,verifies if it has Internet connectivity using that hotspot. Suchfunctionality may, for example, be implemented in an independent processand/or may be implemented as part of any of the other processesdiscussed herein (e.g., with regard to the Connection Management Entitydiscussion). In an example scenario, only after the guarantee ofInternet connectivity through the Wi-Fi hotspot is the Wi-Fi hotspotinformation updated to show that the connection is available.

Depending on commercial agreements, if relied upon, performing anauthentication procedure may be required before association with theWi-Fi network is allowed. For example, in an example scenario in whichthe Wi-Fi hotspot is a private hotspot, a commercial agreement may beestablished between the operator of the vehicle network and the operatorof the Wi-Fi hotspot by which various nodes of the vehicle network(e.g., Fixed APs, Mobile APs, etc.) may access the Internet via theWi-Fi hotspot.

Depending on the type of service being provided, the new Wi-Ficonnection can be used to offload any of a variety of different types oftraffic. For example, the new Wi-Fi connection may be utilized tooffload delay-tolerant information, downloading content from the cloudinfrastructure, software updates, etc.

While a connection is being utilized, the connection manager (e.g., theCME 710 or other entity) may continually analyze the quality of theconnection (e.g., utilizing a Monitor block 703) and determine when tostop utilizing the connection and/or switch to another Wi-Fi hotspot ifavailable and/or another technology. For example, when it is determinedthat the Wi-Fi connection quality is below a threshold level, theconnection manager may identify and establish the next connection. In anexample scenario in which the search for other network connections iscontinual (or, for example, periodic with a search period), theconnection manager may have already identified the next connection bythe time it is determined that the current connection should bereplaced.

As discussed herein, a process of the AP node (e.g., a CME process orother process) may continually (or periodically) run, searching forand/or utilizing a best Wi-Fi hotspot connection. FIG. 9 shows a blockdiagram of an example control method, in accordance with various aspectsof the present disclosure. The example method 900 (or a network or oneor more network components operating in accordance with such method 900)may, for example, share any or all characteristics with the otherexample networks and/or network components 100, 200, 300, 400, 500-570,600, 700, 800, and 1000 discussed herein.

In an example implementation, the Wi-Fi networks to search for can beselected based on commercial agreements between the company operatingthe APs and the company operating the Wi-Fi hotspots. Moreover, aperformance history of the Wi-Fi hotspots in a given location can alsobe kept and updated (e.g., locally, in cloud services, etc.) so that theAPs may connect to the best hotspots. For the given location, the AP mayfor example consult a database which returns a ranked list of the bestWi-Fi hotspots to which the AP may connect at that location or area. Theexample method 900 may, at block 910, comprise receiving (or loading orstoring) a list of hotspots historically utilized and/or authorized tobe utilized at or near a particular area. Note that the list maycomprise public hotspots, private hotspots (e.g., of cooperatingbusiness or individuals, etc.), Mobile and/or Fixed APs, any combinationthereof, etc.

At block 920, the AP may then traverse the list of hotspots, for exampletraversing a ranked list until a Wi-Fi connection with the highestranked hotspot is found, traversing the entire list of hotspots andidentifying a best hotspot, etc. The AP may, for example, search for andanalyze a respective Wi-Fi connection for any or all entries of thelist. The AP may also, for example, search for and analyze Wi-Ficonnections for hotspots that are not on the list. The AP may identify abest or favorite hotspot in any of a variety of manners and/or inaccordance with any of a variety of metrics, many examples of which areprovided herein (e.g., signal strength, load, location, Mobile APvelocity, error rate, number of other nodes connected, historicalexperience with the hotspot, cost of utilizing the hotspot, estimatedtime to be within range of the hotspot, etc.). As indicated by flow line925, the AP may continue scanning until a hotspot determination is made.

After detecting (or determining) the most suitable Wi-Fi hotspot, the APmay, for example at block 930, comprise performing link level (or layer)association. A continuous evaluation of the link-level association maythen be performed, for example as indicated by flow line 935, in orderto notify the connection manager as soon as possible whenever the Wi-Fihotspot signal has been lost or has become too weak or otherwiseinadequate. If the connection is lost while performing the link level(or layer) association, then flow of the example method 900 proceeds toblock 970, at which the Connection Manager is updated with the currentconnection status.

Note that although various examples presented herein discuss using Wi-Fihotspots run by others, the operator of the network of moving things(e.g., a vehicle network, etc.) may also install Wi-Fi hotspots atparticular advantageous locations and strategically utilize such Wi-Fihotspots. For example, bus stops, fuel depots, dumping stations,maintenance locations, high-traffic areas, notoriously busyintersections, etc., may be equipped with Wi-Fi hotspots.

After the association phase, the example method 900, for example atblock 940, comprise checking for Internet connectivity, which amongother things, allows the AP to determine whether the Wi-Fi interface ofthe AP has a valid network configuration. If so, then flow of theexample method 900 proceeds to block 950, concluding that the Wi-Ficonnection is ready, and to block 960, updating the Connection Managerabout the new state of the Wi-Fi connection.

In an example scenario in which the AP is correctly associated with aWi-Fi hotspot but not capable of connecting to the Internet, flow of theexample method 900 proceeds to block 960, at which the AP performsauthentication. The initial list of Wi-Fi hotspots that the AP retrievesfrom the cloud (and/or from a locally maintained list) may for examplehave the login information for the hotspots that may requireauthentication. Since the authentication process may, for example, addan extra delay and requires a good connection to be successful, theexample method 900 allows the authentication process to be repeated(e.g., until a certain number of failed attempts) provided that the APkeeps connected to the same hotspot. Such repetition is showngraphically in FIG. 9 at flow line 965.

At block 970, the Connection Manager is notified about the availabilityof the Wi-Fi connection and, depending on the service constraints, maythen select the Wi-Fi interface as the default communication interface,for example until the connection is lost (or degraded to a particularlevel) or a better connection appears.

In accordance with various aspects of the present disclosure, acommunication network of moving things may, for example, leverage thecapabilities of a wide-ranging and often under-exploited wirelessinfrastructure as a backhaul. Various aspects of the disclosure providea system and method that opportunistically utilizes Wi-Fi resources(e.g., of public networks, of the private networks of others, and evenof the network operator). The various aspects provide for cost-effectiveAP deployment, low-cost information off-load (e.g., from the Mobile APsto the cloud), low-cost information dissemination (e.g., from the cloudto the Mobile APs), and decreases the average overall time fortransporting information to the cloud. Additionally, connectivity rangefor the moving network is improved without having to deploy additionalfixed infrastructure.

Note that the Wi-Fi connectivity may be incorporated into mobilityand/or hand-off algorithms. For example, an on-going connection for aMobile AP may be passed from a first Wi-Fi hotspot to a fixed 802.11pAP, to a Mobile AP, to a second Wi-Fi hotspot, to a cellular link, etc.Also for example, an on-going connection may be handed off from a firstWi-Fi hotspot operated by a first operator to a second Wi-Fi hotspotoperated by a second operator (e.g., utilizing various technologies, forexample, Wi-Fi Passpoint, 802.11u, etc.).

FIG. 10 shows a block diagram of various components of an examplenetwork node, in accordance with various aspects of the presentdisclosure. The example node 1000 may, for example, share any or allcharacteristics with the other example methods, networks, and/or networkcomponents 100, 200, 300, 400, 500-570, 600, 700, 800, and 900,discussed herein. For example, any or all of the components of theexample node 1000 may perform any or all of the method steps presentedherein.

Though labeled “Mobile AP,” the network node 1000 may, for example,comprise an access point (AP) node (e.g., a Mobile AP, a Fixed AP,etc.), any node presented herein, etc. The example node 1000 maycomprise a variety of components (or modules), non-limiting examples ofwhich are provided herein.

The example node 1000 may, for example, comprise a communicationinterface (I/F) module 1020 (e.g., including a cellular communicationinterface module, mobile network communication interface module, Wi-Ficommunication interface module, user/client communication interfacemodule, etc.) that operates to perform any or all of the wireless and/orwired communication functionality for the node 1000, many examples ofwhich are provided herein (e.g., communication with sensors external tothe node 1000, communication with the onboard diagnostic (OBD) system ofa vehicle in which the node 1000 is installed, communication with peerAPs, communication between Mobile APs and Fixed APs, communication withNetwork Controllers, communication with client devices, backhaulcommunication, Cloud server communication, etc.). The communicationinterface (I/F) module 1020 may, for example, operate in accordance withany of a variety of cellular communication protocols, 3G, 4G, LTE,wireless LAN communication protocols (e.g., Wi-Fi, etc.), wireless PANcommunication protocols (e.g., Bluetooth, etc.), 802.11p or DSRC,satellite communication protocols, fiber or cable communicationprotocols, LAN protocols (e.g., Ethernet, etc.), TCP/IP, etc.

The example node 1000 may, for example, comprise a Connection ManagementEntity (CME) 1030 that operates to perform any or all of the connectionmanagement functionality discussed herein. The example CME 1030 may, forexample, comprise hardware and/or software that operate to implement anyor all of the node's connection management functionality discussedherein. For example, the CME 1030 may share any or all characteristicswith the CME 710 and/or system 700 of FIG. 7, discussed herein. Also forexample, the CME 1030 may operate to perform any or all blocks of theexample method 900 of FIG. 9, discussed herein.

The example node 1000 may, for example, comprise a Master Control Module1010 that generally manages operation of the node 1000 at a high level.Such Master Control Module 1010 may, for example, comprise variousaspects of an operating system for the node 1000.

The example node 1000 may further, for example, comprise one or moreapplications 1050 executing on the node 1000 (e.g., client managementapplications, security applications, power management applications,vehicle monitoring applications, location services applications, sensorinterface applications, etc.).

The example node 1000 may also comprise one or more processors 1080 andmemory devices 1090. The processor(s) 1080 may, for example, compriseany of a variety of processor characteristics. For example, theprocessor(s) 1080 may comprise one or more of a general purposeprocessor, RIS processor, microcontroller, ASIC, DSP, video processor,etc.). The memory device(s) 1090 may, for example comprise any of avariety of memory characteristics. For example, the memory device(s)1090 may comprise a volatile memory, non-volatile memory, etc. Thememory device(s) 1090 may, for example, comprise a non-transitorycomputer-readable medium that comprises software instructions that whenexecuted by the processor(s) 1080, cause the node 1000 (or modules orentities thereof) to perform any or all of the functionality discussedherein (e.g., with regard to the example methods discussed herein,etc.). The memory device(s) 1090 may, for example, store nodeinformation (e.g., CNL information, Wi-Fi hotspot list information, NIBinformation, configurable cost function information, etc.).

In accordance with various aspects of this disclosure, examples of thenetworks and/or components thereof presented herein are provided in U.S.Provisional Application Ser. No. 62/222,192, titled “CommunicationNetwork of Moving Things,” filed on Sep. 22, 2015.

In accordance with various aspects of this disclosure, the networksand/or components thereof presented herein are provided with systems andmethods for integrating such networks and/or components with othernetworks and systems, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/221,997, titled “IntegratedCommunication Network for A Network of Moving Things,” filed on Sep. 22,2015, which is hereby incorporated herein by reference in its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for synchronizing such networks and/or components,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/222,016, titled “Systems and Methods forSynchronizing a Network of Moving Things,” filed on Sep. 22, 2015, whichis hereby incorporated herein by reference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing such networks and/or components,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/222,042, titled “Systems and Methods forManaging a Network of Moving Things,” filed on Sep. 22, 2015, which ishereby incorporated herein by reference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for monitoring such networks and/or components,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/222,066, titled “Systems and Methods forMonitoring a Network of Moving Things,” filed on Sep. 22, 2015, which ishereby incorporated herein by reference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for detecting and/or classifying anomalies insuch networks and/or components, non-limiting examples of which areprovided in U.S. Provisional Application Ser. No. 62/222,077, titled“Systems and Methods for Detecting and Classifying Anomalies in aNetwork of Moving Things,” filed on Sep. 22, 2015, which is herebyincorporated herein by reference in its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing mobility in such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,098, titled “Systems and Methodsfor Managing Mobility in a Network of Moving Things,” filed on Sep. 22,2015, which is hereby incorporated herein by reference in its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing connectivity in such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,121, titled “Systems and Methodsfor Managing Connectivity a Network of Moving Things,” filed on Sep. 22,2015, which is hereby incorporated herein by reference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for collecting sensor data in such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,135, titled “Systems and Methodsfor Collecting Sensor Data in a Network of Moving Things,” filed on Sep.22, 2015, which is hereby incorporated herein by reference in itsentirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for interfacing with such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,145, titled “Systems and Methodsfor Interfacing with a Network of Moving Things,” filed on Sep. 22,2015, which is hereby incorporated herein by reference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for interfacing with a user of such networksand/or components, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,150, titled “Systems and Methodsfor Interfacing with a User of a Network of Moving Things,” filed onSep. 22, 2015, which is hereby incorporated herein by reference in itsentirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for data storage and processing in such networksand/or components, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,168, titled “Systems and Methodsfor Data Storage and Processing for a Network of Moving Things,” filedon Sep. 22, 2015, which is hereby incorporated herein by reference inits entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for vehicle traffic management in such networksand/or components, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,183, titled “Systems and Methodsfor Vehicle Traffic Management in a Network of Moving Things,” filed onSep. 22, 2015, which is hereby incorporated herein by reference in itsentirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for environmental management in such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,186, titled “Systems and Methodsfor Environmental Management in a Network of Moving Things,” filed onSep. 22, 2015, which is hereby incorporated herein by reference in itsentirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing port or shipping operation in suchnetworks and/or components, non-limiting examples of which are providedin U.S. Provisional Application Ser. No. 62/222,190, titled “Systems andMethods for Port Management in a Network of Moving Things,” filed onSep. 22, 2015, which is hereby incorporated herein by reference in itsentirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for enhancing the accuracy of positioning orlocation information based at least in part on historical data,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/244,828, titled “Utilizing Historical Data toCorrect GPS Data in a Network of Moving Things,” filed on Oct. 22, 2015,which is hereby incorporated herein by reference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for enhancing the accuracy of position or locationof positioning or location information based at least in part on theutilization of anchors, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/244,930, titled “Using Anchorsto Correct GPS Data in a Network of Moving Things,” filed on Oct. 22,2015, which is hereby incorporated herein by reference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for providing communication between applications,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/246,368, titled “Systems and Methods forInter-Application Communication in a Network of Moving Things,” filed onOct. 26, 2015, which is hereby incorporated herein by reference in itsentirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for probing, analyzing and/or validatingcommunication, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/246,372, titled “Systems and Methodsfor Probing and Validating Communication in a Network of Moving Things,”filed on Oct. 26, 2015, which is hereby incorporated herein by referencein its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for adapting communication rate, non-limitingexamples of which are provided in U.S. Provisional Application Ser. No.62/250,544, titled “Adaptive Rate Control for Vehicular Networks,” filedon Nov. 4, 2015, which is hereby incorporated herein by reference in itsentirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for reconfiguring and adapting hardware,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/273,878, titled “Systems and Methods forReconfiguring and Adapting Hardware in a Network of Moving Things,”filed on Dec. 31, 2015, which is hereby incorporated herein by referencein its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for optimizing the gathering of data, non-limitingexamples of which are provided in U.S. Provisional Application Ser. No.62/253,249, titled “Systems and Methods for Optimizing Data Gathering ina Network of Moving Things,” filed on Nov. 10, 2015, which is herebyincorporated herein by reference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for performing delay tolerant networking,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/257,421, titled “Systems and Methods for DelayTolerant Networking in a Network of Moving Things,” filed on Nov. 19,2015, which is hereby incorporated herein by reference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for improving the coverage and throughput ofmobile access points, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/265,267, titled “Systems andMethods for Improving Coverage and Throughput of Mobile Access Points ina Network of Moving Things,” filed on Dec. 9, 2015, which is herebyincorporated herein by reference in its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for coordinating channel utilization, non-limitingexamples of which are provided in U.S. Provisional Application Ser. No.62/270,858, titled “Channel Coordination in a Network of Moving Things,”filed on Dec. 22, 2015, which is hereby incorporated herein by referencein its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for implementing a network coded mesh network in thenetwork of moving things, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/257,854, titled “Systems andMethods for Network Coded Mesh Networking in a Network of MovingThings,” filed on Nov. 20, 2015, which is hereby incorporated herein byreference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for improving the coverage of fixed access points,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/260,749, titled “Systems and Methods forImproving Fixed Access Point Coverage in a Network of Moving Things,”filed on Nov. 30, 2015, which is hereby incorporated herein by referencein its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing network (or mobility) controllers andtheir network interactions, non-limiting examples of which are providedin U.S. Provisional Application Ser. No. 62/273,715, titled “Systems andMethods for Managing Mobility Controllers and Their Network Interactionsin a Network of Moving Things,” filed on Dec. 31, 2015, which is herebyincorporated herein by reference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for managing and/or triggering handovers ofmobile access points, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/281,432, titled “Systems andMethods for Managing and Triggering Handovers of Mobile Access Points ina Network of Moving Things,” filed on Jan. 21, 2016, which is herebyincorporated herein by reference in its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for performing captive portal-related control andmanagement, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/268,188, titled “CaptivePortal-related Control and Management in a Network of Moving Things,”filed on Dec. 16, 2015, which is hereby incorporated herein by referencein its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for extrapolating high-value data, non-limitingexamples of which are provided in U.S. Provisional Application Ser. No.62/270,678, titled “Systems and Methods to Extrapolate High-Value Datafrom a Network of Moving Things,” filed on Dec. 22, 2015, which ishereby incorporated herein by reference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for providing remote software updating anddistribution, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/272,750, titled “Systems and Methodsfor Remote Software Update and Distribution in a Network of MovingThings,” filed on Dec. 30, 2015, which is hereby incorporated herein byreference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for providing remote configuration updating anddistribution, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/278,662, titled “Systems and Methodsfor Remote Configuration Update and Distribution in a Network of MovingThings,” filed on Jan. 14, 2016, which is hereby incorporated herein byreference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for adapting the network, for exampleautomatically, based on user feedback, non-limiting examples of whichare provided in U.S. Provisional Application Ser. No. 62/286,243, titled“Systems and Methods for Adapting a Network of Moving Things Based onUser Feedback,” filed on Jan. 22, 2016, which is hereby incorporatedherein by reference in its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for enhancing and/or guaranteeing data integritywhen building or performing data analytics, non-limiting examples ofwhich are provided in U.S. Provisional Application Ser. No. 62/278,764,titled “Systems and Methods to Guarantee Data Integrity When BuildingData Analytics in a Network of Moving Things,” Jan. 14, 2016, which ishereby incorporated herein by reference in its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for performing self-initialization and/or automatedbootstrapping of mobile access points, non-limiting examples of whichare provided in U.S. Provisional Application Ser. No. 62/286,515, titled“Systems and Methods for Self-Initialization and Automated Bootstrappingof Mobile Access Points in a Network of Moving Things,” filed on Jan.25, 2016, which is hereby incorporated herein by reference in itsentirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing power supply and/or utilization,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/295,602, titled “Systems and Methods for PowerManagement in a Network of Moving Things,” filed on Feb. 16, 2016, whichis hereby incorporated herein by reference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for automating and easing the installation and setupof the infrastructure, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/299,269, titled “Systems andMethods for Automating and Easing the Installation and Setup of theInfrastructure Supporting a Network of Moving Things,” filed on Feb. 24,2016, which is hereby incorporated herein by reference in its entirety.

In summary, various aspects of this disclosure provide systems andmethods for managing connectivity in a network of moving things. Asnon-limiting examples, various aspects of this disclosure providesystems and methods for managing connectivity in a network in which atleast a portion of the network access points are moving. While theforegoing has been described with reference to certain aspects andexamples, it will be understood by those skilled in the art that variouschanges may be made and equivalents may be substituted without departingfrom the scope of the disclosure. In addition, many modifications may bemade to adapt a particular situation or material to the teachings of thedisclosure without departing from its scope. Therefore, it is intendedthat the disclosure not be limited to the particular example(s)disclosed, but that the disclosure will include all examples fallingwithin the scope of the appended claims.

1-30. (canceled)
 31. A vehicle communication network access pointcomprising: at least one wireless transceiver; and at least one modulecomprising a processor and memory, and being operable to, at least:utilize the at least one wireless transceiver to provide wireless localarea network (WLAN) connectivity to client devices of the access point;identify a location of the access point; identify a hotspot based, atleast in part, on the identified location of the access point; andutilize the at least one wireless transceiver to: attempt to establish acommunication link with the identified hotspot; and if said attempt issuccessful, then communicate data with another network node via theidentified hotspot.
 32. The vehicle communication network access pointof claim 31, wherein the at least one module is operable to identify thehotspot by, at least in part, consulting a database based on theidentified location.
 33. The vehicle communication network access pointof claim 32, wherein the database is stored in the memory of the accesspoint.
 34. The vehicle communication network access point of claim 32,wherein: the database is remote from the access point; and the at leastone module is operable to consult the database through the vehiclecommunication network.
 35. The vehicle communication network accesspoint of claim 32, wherein the at least one module is operable toconsult the database by, at least in part, consulting the database for ahotspot historically utilized by the access point at the identifiedlocation.
 36. The vehicle communication network access point of claim31, wherein the identified hotspot is a highest ranked hotspotassociated with the identified location.
 37. The vehicle communicationnetwork access point of claim 31, wherein the at least one module isoperable to: if the identified hotspot is a public hotspot, thenestablish a communication link with the identified hotspot according toa first protocol for establishing a communication link; and if theidentified hotspot is a private hotspot, then establish a communicationlink with the identified hotspot using a second protocol, different fromthe first protocol, for establishing a communication link.
 38. Thevehicle communication network access point of claim 31, wherein theidentified hotspot comprises a WLAN hotspot.
 39. The vehiclecommunication network access point of claim 31, wherein: the at leastone wireless transceiver comprises a first wireless transceiver and asecond wireless transceiver; and the at least one module is operable toutilize the first wireless transceiver to communicate with theidentified hotspot, while simultaneously utilizing the second wirelesstransceiver to provide the WLAN connectivity to the client devices ofthe access point.
 40. The vehicle communication network access point ofclaim 31, wherein the at least one module is operable to offload trafficcommunicated with the vehicle communication network to the identifiedhotspot.
 41. The vehicle communication network access point of claim 31,wherein the access point is mobile.
 42. The vehicle communicationnetwork access point of claim 31, wherein the at least one module isoperable to: monitor performance of the identified hotspot at theidentified location; and store information describing the monitoredperformance of the identified hotspot in the memory.
 43. A vehiclecommunication network access point comprising: at least one wirelesstransceiver; and at least one module comprising a processor and memory,and being operable to, at least: utilize the at least one wirelesstransceiver to provide wireless local area network (WLAN) connectivityto client devices of the access point; identify a location of the accesspoint, wherein the access point is mobile; identify a hotspot based, atleast in part, on the identified location of the access point; andutilize the at least one wireless transceiver to: attempt to establish acommunication link with the identified hotspot; and if said attempt issuccessful, then communicate data with another network node via theidentified hotspot.
 44. The vehicle communication network access pointof claim 43, wherein the at least one module is operable to identify thehotspot based, at least in part, on velocity of the access point. 45.The vehicle communication network access point of claim 43, wherein theat least one module is operable to identify the hotspot based, at leastin part, on vehicle route information for a vehicle carrying the accesspoint.
 46. The vehicle communication network access point of claim 43,wherein the at least one module is operable to identify the hotspotbased, at least in part, on an estimated time for the access point to bewithin communication range of the identified hotspot.
 47. The vehiclecommunication network access point of claim 43, wherein the at least onemodule is operable to identify the hotspot by, at least in part,consulting a remote database via the vehicle communication network, andwherein said consulting the remote database comprises consulting theremoted database based on the identified location.
 48. The vehiclecommunication network access point of claim 43, wherein: the at leastone wireless transceiver comprises a first wireless transceiver, asecond wireless transceiver, and a third wireless transceiver; the atleast one module is operable to utilize the first wireless transceiverto communicate with another access point of the vehicle communicationnetwork, while utilizing the second wireless transceiver to provide theWLAN connectivity to the client devices, and while utilizing the thirdwireless transceiver to communicate with the identified hotspot.
 49. Avehicle communication network access point comprising: at least onewireless transceiver; and at least one module comprising a processor andmemory, and being operable to, at least: utilize the at least onewireless transceiver to provide wireless local area network (WLAN)connectivity to client devices of the access point; receive a list ofhotspots; identify a location of the access point; identify a hotspotbased, at least in part, on the identified location of the access point;and utilize the at least one wireless transceiver to: attempt toestablish a communication link with the candidate best hotspot; and ifsaid attempt is successful, then communicate data with another networknode via the candidate best hotspot.
 50. The vehicle communicationnetwork access point of claim 49, wherein the list of hotspots is rankedfor the identified location.
 51. The vehicle communication network ofclaim 49, wherein the at least one module is operable to identify thehotspot by, at least in part, traversing the list of hotspots.
 52. Thevehicle communication network of claim 49, wherein the identifiedhotspot is not on the list of hotspots.
 53. The vehicle communicationnetwork of claim 49, wherein the at least one module is operable to:monitor performance of the identified hotspot at the identifiedlocation; and modify the received list of hotspots based, at least inpart, on the monitored performance of the identified hotspot.